speclisted

# spec — analyze and execute a spec Load before any feature/spec/roadmap build. Missing spec -> author via `docs`. Analyze before code; ask FnB on ambiguity, flag hard blockers. `<self>` = your shell id. ## 1. Select the spec Never auto-pick the latest document. Read the complete selected body + task ledger: ```text sc mem get documents --feature <id> sc mem get documents --doc <doc_id> sc mem get tasks --doc <doc_id> ``` The list includes `kind`, `seq`, `frozen`, and `task_count`. Resume the unfrozen spec with tasks; zero tasks = backlog and needs the plan below. Multiple plausible specs -> ask FnB. Existing tasks -> track the first unfinished one. ## 2. Analyze before planning Return these findings before any code or task writes: | Check | Pass condition / action | |---|---| | Viability | Bounded, clear entry points, session-sized verification. Otherwise propose a verifiable slice. Missing done-condition = unclear. | | Current Posture | Preparation code/DB state matches the documented baseline. A mismatch stops for Planner/FnB; never redefine it silently. | | Scope | Every In Scope promise is planned; every Out of Scope item stays out. New/substantively revised specs contain both `## Current Posture` and `## Scope`; ambiguity stops. | | Anticipated User Activity | Plan stated roles, audience/reach, access, validation, recovery, authority, safety, process curation, and tenancy invariants. Older absence is allowed; ambiguity is not. | | Unclear item | Two plausible re