goalforge-onboardlisted

# goalforge-onboard Bootstraps the SDD chain in a repository. Three idempotent steps: 1. **Create `plans/`** — creates `plans/README.md` at the repo root if `plans/` is absent; leaves it untouched if it already exists. 2. **Install the pre-commit hook** — delegates entirely to `goalforge-install-hooks.sh`, which handles the chain-safe append-to-existing-hook case and the idempotency marker (`# >>> sdd-pre-commit >>>`). 3. **Stamp `## SDD` into `CLAUDE.md`** — appends a pointer block documenting the chain, plans root, hook, and status vocabulary. Creates a minimal `CLAUDE.md` if none exists; skips if a `## SDD` heading is already present. ## Usage ```bash bash ${CLAUDE_PLUGIN_ROOT}/skills/onboard/scripts/goalforge-onboard.sh [<repo-dir>] ``` `<repo-dir>` defaults to `git rev-parse --show-toplevel` from the current working directory. Aborts with a clear message if the target is not a git repository. ## What it delegates Hook installation is fully delegated to the existing installer: ``` ${CLAUDE_PLUGIN_ROOT}/scripts/goalforge-install-hooks.sh <repo-dir> ``` `goalforge-onboard` does not reimplement hook logic. ## Gotchas - **Current vocabulary only.** The stamped `## SDD` block uses the current status vocabulary: WPs `draft→spec→hardened→ready→executing→verified`; tasks `pending→in-progress→implemented→verified` (`implemented` is the interim post-eval+commit state; `verified` is written only at the WP gate by `goalforge-verify`). It does NOT ref