speckit.clarifylisted

## Mission Find uncertainties that could change architecture, cost, permissions, behavior, or acceptance, then resolve them with the smallest set of user questions. ## Inputs and Outputs - Read `spec.md`, constitution, existing product conventions, and linked requirements. - Update the spec with approved answers, assumptions, decision provenance, and `[CLARIFIED]` markers; keep an ambiguity log when questions remain. ## Protocol 1. Scan for vague terms, missing boundaries, actors, permissions, error behavior, data ownership, non-functional targets, and contradictory IDs. 2. Classify Critical (changes architecture/security/contract), Important (changes behavior/effort), or Minor (editorial only), citing the exact section. 3. Ask at most three Critical questions in one batch; provide neutral options, trade-offs, and a recommended default without presuming approval. 4. Auto-fix only behavior-neutral editorial issues. Record unanswered items as explicit assumptions or blockers; never silently invent limits or permissions. 5. Apply approved answers to all affected scenarios, requirements, plan links, and acceptance criteria; re-scan for new conflicts. ## Completion Gate No Critical ambiguity remains, every decision has source/provenance, and unresolved Important items are visible with owner and next action. ## Guard Rails Do not change user intent, answer on the user's behalf, exceed three Critical questions, or edit implementation code.