What problem does it solve?
Starting development without clear, agreed-upon requirements leads to misaligned features, wasted coding effort, and costly rework when stakeholders find the final output does not match their expectations.
Core Features & Use Cases
- Guided Requirement Gathering: Asks targeted clarifying questions to capture project objectives, target users, core features, tech stack constraints, and explicit project boundaries to eliminate all ambiguity.
- Structured Spec Generation: Compiles all gathered information into a standardized SPEC.md file that covers objectives, commands, project structure, code style, testing strategy, and boundaries.
- Use Case: When building a new customer-facing checkout flow, use this skill to first document required payment methods, fraud prevention rules, and error handling logic before writing any implementation code.
Quick Start
Use the spec skill to gather all requirements for your new user authentication feature, generate a structured SPEC.md file, save it to your project's _mission-control folder, and get stakeholder approval before starting any implementation work.