create-epics-stories

To generate user stories from a PRD, input both the complete product requirements document and architecture document into the workflow. The system processes these high-level specifications to decompose complex requirements into organized epics and granular user stories with contextual integration.

Yes, you can automatically create acceptance criteria for agile development stories. The workflow analyzes your technical and design context to generate comprehensive acceptance criteria for each user story, ensuring development teams have implementation-ready clarity.

The best way to break down complex product requirements into epics is by processing complete PRD and architectural decisions together. This requirement decomposition bridges the gap between high-level specifications and actionable development tasks, yielding organized epics for the engineering backlog.

Yes, you need a complete PRD and architecture documentation as input to generate implementation-ready stories. The workflow relies on fully specified product requirements and architectural decisions to accurately create granular user stories with comprehensive acceptance criteria.

Requirement decomposition handles technical context through contextual integration. It incorporates technical and design context directly from your PRD and architecture documents into the user story definitions, ensuring the generated development tasks align with architectural constraints.

A key limitation is the strict dependency on complete input documentation. Without fully detailed PRD and architecture documents, the workflow cannot accurately generate implementation-ready epics, granular user stories, or the associated acceptance criteria for the development backlog.