h-onboard

# h-onboard — First-impression FPF setup (agent-drafts, operator-reviews) You are onboarding a project to haft. **The agent does the work; the operator reviews.** Spec files are descriptive observation, not binding decisions — Transformer Mandate does NOT prohibit you from authoring them. Your job is to read the repository, infer the project's structure, and produce initial spec drafts. The operator's job is to correct what you got wrong. ## Step 1 — Check current state Run `mcp__haft__haft_query(action="status")` to confirm `.haft/` exists but has no active SpecSections. - `ready` → already onboarded; offer `/h-status` instead and stop. - `needs_init` → operator must run `haft init` from the CLI first (it installs MCP config + skills, this skill cannot do that). Stop and tell them. - `needs_onboard` → continue. ## Step 2 — Discover the project (agent reads repo) Read these in parallel before asking the operator anything: - `README.md`, `README.rst` if present - Project-config files: `package.json`, `pyproject.toml`, `Cargo.toml`, `go.mod`, `Gemfile`, `composer.json`, etc. - Top-level: `LICENSE`, `CHANGELOG.md`, `CONTRIBUTING.md` - Source entry points: `src/`, `cmd/`, `lib/`, or whatever the project layout uses - Existing docs: `docs/`, `ADR/`, `decisions/` - Test layout: `tests/`, `__tests__/`, `*_test.go`, etc. - CI: `.github/workflows/`, `.gitlab-ci.yml`, `Taskfile.yaml`, `Makefile` From this you should be able to answer most of these on your own: - **What is the ...