spec-done

# `spec done` — mark a task complete CLI at `scripts/specctl`. Three flavors: - **Mark a specific task done** — user names a task and says it's finished. - **Discover potentially done tasks** — user wants to know which in-progress tasks look complete based on git evidence. - **Verify then mark** — user wants tests/lint/build to pass before changing status. ## Mark a specific task ### Step 1: Find the task Look up the task file under `.spec/tasks/` matching the user-supplied id (add the `TASK-` prefix if missing). If not found, say "Task not found." and stop. ### Step 2: Check current status If the task is already `done`, say "Already complete." and stop. Otherwise continue. ### Step 3: Verify completion evidence Before marking done, collect or confirm: - Acceptance criteria satisfied - Test / lint / build evidence (or an explicit reason they were not run) - Files changed - Unresolved follow-up work - Any domain term, ADR, or out-of-scope decision discovered If evidence is missing, ask the user before marking done. ### Step 4: Update status Edit the task frontmatter: `status: todo` → `status: done`. ### Step 5: Log ```bash echo "$(date +%H:%M) DONE TASK-<id>" >> .spec/PROGRESS.md ``` Output: ``` ## Done Marked complete: TASK-<id> ``` ### Step 6: Land the plane Check for uncommitted work: ```bash git status --porcelain ``` If non-empty, offer to commit (delegate to the runtime's commit workflow). Record durable decisions if needed: - New domain term → `C...