write-story

To write user stories with acceptance criteria, input your feature description and project context. The system automatically drafts a structured user story with clear titles, bodies, and testable acceptance criteria ready for development.

INVEST validation in agile story writing checks if a user story is Independent, Negotiable, Valuable, Estimable, Small, and Testable. The system automatically validates your stories against these criteria to ensure they are ready for backlog refinement.

To refine incomplete user stories, the system reads project context like roadmaps and CLAUDE.md files, then prompts you for underspecified dimensions. This contextual refinement ensures stories are actionable and technically informed before development.

Yes, you can generate agile user stories that include technical notes. By analyzing your project context and feature descriptions, the tool incorporates relevant technical considerations directly into the generated story details.

The best way to ensure user stories are small and testable is using automated INVEST validation. This process checks each story against specific criteria, prompting iterative refinement until the story is properly sized and testable.

Yes, automated story writing supports iterative refinement. It performs automated checks on your feature descriptions and actively prompts you to clarify underspecified dimensions, ensuring the final user story is fully actionable.