user-story-builder

To convert a raw product idea into a user story, provide the initial concept to trigger a phase-driven clarification process. This guides you through defining who, what, and why, drafting a narrative, and iterating until you confirm alignment.

Writing acceptance criteria for ambiguous requirements involves a phase-driven clarification process that defines who, what, and why. The system drafts a template and refines it iteratively with you until the acceptance criteria are clear and aligned.

INVEST criteria for product management user stories ensures requirements are Independent, Negotiable, Valuable, Estimable, Small, and Testable. This skill enforces INVEST compliance while drafting your narrative to guarantee a well-defined, ready-to-implement story.

You can align with stakeholders before development begins through iterative refinement. The skill facilitates problem understanding and drafts the story, prompting confirmation from all parties to ensure alignment before outputting the final story block.

The best way to structure a user story template is using a phase-driven approach that clarifies the who, what, and why. This yields a final story block containing a title, narrative, acceptance criteria, and scope notes.