What problem does it solve? Writing software specifications often produces vague, untestable, or incomplete requirements that drift from the approved proposal. This Skill enforces a rigid four-phase workflow that turns an approved OpenSpec proposal into a complete, testable specification with Gherkin scenarios before any design or implementation begins. ## Core Features & Use Cases - Interactive Requirement Analysis: Runs a seven-step analysis (context, extraction, completeness, ambiguity, edge cases, stakeholders, scenarios) asking one question at a time so no gap is silently assumed. - Gherkin Scenario Enforcement: Requires every functional requirement to carry uppercase GIVEN/WHEN/THEN scenarios covering positive, negative, and edge cases. - Drift Check and Compliance Review: Verifies the spec against the proposal and design, then dispatches a single-shot reviewer subagent to catch placeholders, contradictions, and template violations. - Use Case: After approving an OpenSpec change proposal, run the spec phase to produce a specification where every requirement is testable, aligned with the proposal, and reviewed before design work starts. ## Quick Start Ask the AI to create the OpenSpec specification for the current approved change proposal and walk through the requirement analysis questions.