harness-create-epics-and-stories

To break down a PRD into epics and user stories, the Skill extracts functional and non-functional requirements, groups them into user-value epics, and generates stories with testable Given/When/Then acceptance criteria without forward dependencies.

Generating a developer agent-ready backlog from architecture decisions involves ingesting architecture inputs, structuring standalone epics with explicit coverage, and sizing stories per developer agent with strict coverage validation so every functional requirement maps to at least one story.

Yes, you can use this workflow to extract non-functional requirements. It performs requirement decomposition to pull functional, non-functional, and architecture-driven requirements directly from project planning artifacts for backlog generation.

Requirement decomposition ensures every functional requirement maps to a user story through strict coverage validation. It builds an explicit coverage map during epic structuring to guarantee complete FR-to-story traceability.

Yes, you need Python3 to create epics and stories from a PRD. The Skill relies on Python3 and internal scripts to resolve customizations and execute the sequential step generation process for backlog output.

A limitation of AI requirements decomposition is that it requires collaborative confirmation gates at multiple stages. You must manually confirm extracted requirements and proposed epic structures before the full story backlog can be generated.