spec-work

# `spec work` — main implementation workflow CLI at `scripts/specctl`. Full development workflow for one task per session, with user control at every step. Input: empty (next ready task), `EPIC-id` (next ready in that epic), or `TASK-id` (specific task). ## Step 0: Check state ```bash scripts/specctl status 2>/dev/null || echo "NO_SPEC" ``` If `NO_SPEC`: "Use the `spec-init` skill to initialize the project first." Stop. ### Check for interrupted session ```bash scripts/specctl session show 2>/dev/null git branch --show-current 2>/dev/null ``` If a session is in progress, ask the user a multi-choice question: "Found interrupted session: <task> at step <step>. Resume or clear?" - Resume — continue from `<step>` - Clear & pick new — start fresh If resuming, jump to the step recorded in `SESSION.yaml`. ## Step 1: Select task - `TASK-id` argument → use it. - `EPIC-id` argument → `scripts/specctl ready --epic EPIC-id` and pick the highest-priority ready task. - Otherwise → `scripts/specctl ready` and pick the highest-priority ready task. If no ready tasks: ```bash scripts/specctl ready # shows blockers ``` Tell the user: "No tasks ready. Check blocked tasks or create new work." Stop. ### Load task and context ```bash scripts/specctl show TASK-<id> ``` Read the task file. Check for epic link (`epic:` field) and requirement link (`implements:` in the epic). Read when present: - Epic file - Requirement file - `CONTEXT.md`, `CONTEXT-MAP.md`, ADRs - `.out-of-scope/...