task-decomposition

To generate user stories and tasks from a PRD, use a task decomposition process that reads your docs/PRD.md and docs/ARCHITECTURE.md to output a structured docs/TASKS.md file. This translates high-level requirements into epics, stories, and atomic tasks.

The best way to break down epics into atomic tasks is to align them with your architectural design, ensuring each task is independently executable and testable. This yields a hierarchical plan with clear acceptance criteria.

Yes, you can create a sprint-ready task breakdown by processing your existing PRD and architecture documents. The system automatically translates these inputs into a structured engineering plan, producing a shared TASKS.md file.

The task plan output uses a markdown format, specifically generating a docs/TASKS.md file. This document contains the hierarchical breakdown of epics, user stories, and atomic tasks, making it easy to share with stakeholders.

Yes, you need both a PRD and an architecture document to generate a complete task breakdown. The process reads docs/PRD.md and docs/ARCHITECTURE.md to ensure the resulting tasks align with both product requirements and technical design.