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