user-stories

To generate INVEST-compliant user stories from a PRD, provide the approved PRD containing features and personas. The tool extracts personas and outputs stories mapping to acceptance criteria, estimates, and dependencies into a standardized markdown template.

Story splitting for large epics occurs automatically when the tool detects them during PRD processing. It breaks down large epics into smaller, INVEST-compliant user stories to ensure they are testable and ready for sprint planning.

Yes, you need an approved PRD that explicitly includes features and personas. The tool relies on these inputs to extract personas and generate user stories that accurately map to acceptance criteria and dependencies.

Yes, user stories with acceptance criteria and estimates are output directly to docs/user-stories/<feature>/stories.md. This standardized markdown file ensures consistent formatting for sprint planning and cross-cutting considerations.

The best way to prepare user stories for sprint planning is converting approved product requirements into INVEST-compliant stories. This process validates criteria, generates estimates, identifies dependencies, and provides sprint-readiness recommendations.

User stories fail INVEST criteria when they are too large or lack clear acceptance criteria. This tool prevents failures by validating INVEST compliance during generation and applying story splitting to ensure testable, manageable outputs.