spec-status

# spec — status and orientation Read-only entry point for spec-driven development: report progress, or orient the user to the right sub-skill. If `.spec/` doesn't exist, tell the user: "No `.spec/` folder. Use the `spec-init` skill to initialize the project." and stop. ```bash scripts/specctl status 2>/dev/null || echo "NO_SPEC" ``` ## Pipeline `spec-init` → `spec-interview` → `spec-plan` → `spec-work` → `spec-done` (loop until epic complete) `spec-status` reads state at any point. ### Sub-skills - `spec-init` — initialize `.spec/`, or add requirements from an existing doc - `spec-interview` — deep PRD-quality requirement capture via Q&A - `spec-plan` — create an EPIC + vertical-slice TASKs from a requirement or idea - `spec-new` — one-off task or requirement from a template - `spec-work` — implement the next ready task (one per session, user approval at every step) - `spec-done` — mark a task complete with evidence; optionally discover or verify first - `spec-status` — overview, single-task detail, filtered list, or quality audit ### Where to start - No `.spec/` yet → use the `spec-init` skill to initialize the project - Have an idea → use the `spec-interview` skill to capture requirements - Have REQ files → use the `spec-plan` skill to create tasks - Have TASK files → use the `spec-work` skill to implement the next task ### File structure - `.spec/reqs/REQ-*.md` — requirements (WHAT / WHY) - `.spec/epics/EPIC-*.md` — epics grouping related tasks - `.spec/tasks/T...