What problem does it solve? Fuzzy feature ideas and problem statements often jump straight into planning or coding without agreed rules, leading to rework and misaligned expectations. This Skill forces a structured conversation that turns vague intent into shared understanding, concrete examples, and acceptance criteria before any story is split or planned. ## Core Features & Use Cases - Example Mapping: Builds a live map of story, rules, concrete examples, and open questions, written back into the team's existing story artifact (issue, ticket, or docs file). - Accountable Review Rounds: Generates a self-contained HTML review page from a template so owners and risk-relevant stakeholders can annotate rules, parked questions, and candidate vocabulary, with feedback routed back as answers rather than silent edits. - Readiness Diagnostics: Reads the map's shape to decide next steps — question-dominated maps keep the conversation going, rule-dominated maps go to story-splitting, balanced maps are ready to build. - Use Case: A product owner says "users should be able to pause subscriptions." The Skill asks one question at a time, captures rules like "paused subscriptions retain history" with concrete examples, parks unresolved billing questions with owners and dates, and produces acceptance criteria plus a review page for the team. ## Quick Start Ask the agent to spec out a new feature idea by running one question at a time and writing the resulting example map and acceptance criteria into the story's existing artifact.
