What problem does it solve? When a body of work spans multiple stories, teams need an overarching design captured before any stories are written. This Skill turns a feature idea into a structured Feature design doc, preventing fragmented or inconsistent story planning. ## Core Features & Use Cases - Codebase-Aware Exploration: Reads ADRs in docs/decisions/, greps src/ for relevant services and entities, and checks .claude/features/ for overlapping docs before asking questions. - Structured One-at-a-Time Interview: Walks through problem, scope, affected code, dependencies, and an explicit gating decision (none, feature flag, or permanent entitlement). - Design-Only Document Generation: Writes a kebab-case-slugged markdown doc to .claude/features/ with sections for context, goals, architecture, affected files, gating, and constraints, then self-reviews against quality gates. - Use Case: A developer planning a multi-story game verification system uses this Skill to capture the overarching design and gating decision first, then optionally hands off to story-author to generate linked stories. ## Quick Start Ask the AI to author a feature design doc for your feature idea, optionally providing a feature name or short description as an argument.
