spec-init

# `spec init` — initialize or extend a project CLI at `scripts/specctl`. Three modes, picked by checking whether `.spec/` exists and whether the user passed a file path. ## Step 1: Check existing ```bash ls .spec/ 2>/dev/null && echo "SPEC_EXISTS" ``` ## Mode A: New project (no `.spec/`) ### Step 2: Brainstorm If a brainstorming workflow is available in the runtime, use it to surface requirements. Otherwise ask the user directly: - What problem are we solving? - Who are the users? - Core capabilities needed? - Tech stack? Group findings into requirement topics (auth, data, ui, api, etc.). ### Step 3: Confirm Ask the user a multi-choice question: "Does this capture the project?" with options Yes / Adjust / Start over. ### Step 4: Create structure ```bash mkdir -p .spec/reqs .spec/tasks echo "# Progress" > .spec/PROGRESS.md echo "$(date +%H:%M) INIT project" >> .spec/PROGRESS.md ``` Create one `REQ-<topic>.md` per requirement topic: ```markdown --- id: REQ-<topic> version: 1 priority: normal --- # <Title> <Description> <Success criteria> ``` Create initial `TASK-<name>.md` files: ```markdown --- id: TASK-<name> status: todo priority: normal implements: REQ-<topic> --- # <Title> <Vertical slice description, acceptance criteria, out-of-scope boundaries> ``` ### Step 5: Summary ``` ## Ready .spec/ ├── PROGRESS.md ├── reqs/ (<N> requirements) └── tasks/ (<M> tasks) Next: use the `spec-work` skill to start implementing tasks ``` ## Mode B: Add re...