write-user-story

To turn feature notes into user stories, provide a feature description or PRD excerpt. The system outputs ISC-validated stories with distinct user types, single-action behaviors, and Gherkin acceptance criteria for immediate engineering handoff.

Writing user stories with edge cases and anti-requirements requires enforcing ISC-validated formatting. This approach generates one-behavior-per-story, explicitly defines exclusions via anti-requirements, and validates story size to prevent scope creep.

Gherkin acceptance criteria define explicit success and negative paths for each behavior. Applying this to product management ensures cross-functional teams receive handoff-ready artifacts with clear user types and discrete single-action stories without needing further clarification.

Yes, you can generate user stories directly from a PRD section. Processing a feature summary produces comprehensive stories complete with Gherkin-like acceptance criteria, edge cases, and anti-requirements suitable for development handoffs across cross-functional teams.

No, manual sizing is unnecessary when converting feature descriptions. The process enforces size validation inherently, ensuring each generated user story represents a single behavior and remains properly scoped for engineers to start work immediately.