What problem does it solve? Turning a raw Gherkin feature file into an implementation-ready specification is error-prone: requirements get lost, acceptance criteria go untested, and design drifts from the spec. This Skill enforces a gated, two-role (Business Analyst and Solution Architect) analysis pipeline that produces a fully traceable design document for exactly one feature at a time. ## Core Features & Use Cases - Gated multi-phase analysis: Seven phases (scope, business analysis, technical specification, BDD acceptance criteria, Playwright scenario mapping, AC verification matrix, contrarian review), each with a pass/fail gate and revision limits. - Full traceability: Numbered business rules (BR-), design elements (TS-), acceptance criteria (AC-), and Playwright tests (E2E-) cross-referenced in a verification matrix with orphan detection. - Thin-feature shortcut: Features with two or fewer scenarios and no new storage key or module boundary skip the full document and go straight to planning. - Use Case: Given features/005.record-expense.md, run the Skill to produce doc/features/005-record-expense/spec.md containing sourced business rules, a TypeScript data model, Gherkin acceptance criteria, and a Playwright test mapping ready for the implementation loop. ## Quick Start Ask the AI to run /feature-spec 005 to analyze the record-expense feature and write its gated specification document.