user-story-clarifierlisted

# User Story Clarifier Turn rough product intent into a story card that a human or coding agent can implement without guessing. ## When To Use - draft a user story from a rough product idea, ticket, or feature note - rewrite a vague story, definition of done, or acceptance criteria - split a broad story, epic, or feature into smaller story-level slices - audit story-level requirements for ambiguity, missing behavior, or weak testability - tighten a ticket so an implementation agent can plan and execute safely ## Not For - full PRDs, large product specs, ADRs, or long-form design proposals - glossary definitions, terminology cleanup, or generic copy editing - implementation after the story is already clear - broad test strategy where the main question is what evidence is enough ## Core Workflow 1. Classify the mode: draft, rewrite, split, audit, or tighten. 2. Extract the story facts: - actor or user segment - user goal and value - trigger or entry point - expected behavior and visible outcome - data, state, permissions, and constraints - dependencies, assumptions, and non-goals 3. Ask at most 3 focused clarifying questions when the answers would materially change behavior, acceptance criteria, or implementation boundaries. Prioritize actor/outcome, behavior boundary, then acceptance oracle. 4. If clarity is good enough, draft with labeled assumptions instead of asking low-value questions. 5. If the input is too broad for one story, propose th