What problem does it solve? Spec drafts approved without scrutiny surface missed scenarios, contradictions, and untestable success criteria halfway through implementation, causing expensive rework. This Skill performs an independent, read-only critique of a spec draft before the human approves it, catching defects when fixing them costs minutes instead of rework. ## Core Features & Use Cases - Read-Only Critical Review: Reports findings with severity levels (Blocking, Should Fix, Suggestion) without ever editing the spec or any repository file. - Repository-Grounded Analysis: Reviews the draft against the actual code, existing conventions, and previously approved specs in docs/spec/** rather than in a vacuum. - Structured Review Checklist: Verifies success criteria testability, boundary definitions, missed scenarios, contradictions, capability-map coverage, and docs/spec location policy. - Use Case: When the /spec workflow reaches its approve-vs-reflect gate, choose reflection to get a verdict (READY FOR APPROVAL or NEEDS REVISION) with each finding tied to a file/section and the rework it prevents. ## Quick Start Ask the assistant to run a spec reflection review on the draft at docs/spec/my-feature/SPEC.md before approving it.
