What problem does it solve? Teams often jump straight into coding without capturing what a feature should do from the user's perspective, leading to misaligned implementations and lost requirements. This Skill enforces an intent-first workflow by writing implementation-agnostic feature specs before any technical planning occurs. ## Core Features & Use Cases - Intent Spec Generation: Writes structured specs with Context, Desired Behavior, Boundaries, and Success Criteria sections, stored at docs/<feature>/spec.md. - Duplicate Detection: Scans existing docs/**/spec.md files and decides whether a request is a new feature or an update to an existing spec, using a detailed decision framework. - Implementation Gating: Stops after the spec is written and only produces an implementation plan (docs/<feature>/plan.md) when explicitly requested. - Use Case: A product manager says "users should be able to export their data as CSV." The Skill checks existing specs, creates docs/export-data-as-csv/spec.md describing the user experience, and waits before any technical planning. ## Quick Start Ask the assistant to create an intent spec for a new feature you want to add, describing it from the user's perspective.