What problem does it solve? Turning research findings and user brainstorms into a reviewable requirements document is often skipped or done inconsistently, leading to misaligned builds. This Skill produces a structured, user-facing SPEC artifact that captures what the user wants and why before any approach or code is chosen. ## Core Features & Use Cases - Canonical SPEC Generation: Writes a requirements document with nine mandatory sections in fixed order, including user stories, behavioral outcomes, ASCII flow diagrams, and testable acceptance criteria. - Acceptance Criteria Discipline: Every criterion carries a proven by: test scenario and a strategy: annotation, with fully-automated E2E gates required wherever behavior is automatable. - Phase Program Support: Provides an umbrella program SPEC template that governs multi-phase work, written once and frozen once planning begins. - Use Case: After researching a new feature, ask the agent to produce a SPEC so stakeholders can confirm "yes, build that" before INNOVATE or PLAN phases start. ## Quick Start Ask the agent to generate a SPEC for your feature idea based on the completed research findings and your stated intent.
