1 prd_to_epic_decomposition {{task}} {{context}} {{#each requirements}} {{this}} {{/each}} {{allowed_libraries}} {{forbidden_approaches}} {{complexity_limits}} {{integration_requirements}} - Identify functional requirements - Identify non-functional requirements - Identify constraints and dependencies - Identify success criteria - System architecture implications - Database schema requirements - API endpoint needs - Integration requirements - Performance considerations - Security requirements Epic Overview High-level epic summary with objectives and scope Markdown with frontmatter YES Technical Architecture System design addressing PRD requirements Markdown with diagrams YES Task Breakdown Decomposed tasks with dependencies Numbered task list with estimates YES Data Model Database schema and data structures Entity-relationship description or diagram Conditional API Specification Required API endpoints and interfaces Markdown table or OpenAPI spec Conditional Risk Assessment Technical risks and mitigation strategies Markdown list NO Before converting PRD to Epic: 1. ANALYZE THE PRD: - What is the core business objective? - What are the must-have vs nice-to-have features? - What are the technical constraints? - What is the timeline? 2. IDENTIFY TECHNICAL REQUIREMENTS: - What system components are needed? - What data needs to be stored? - What APIs need to be exposed? - What integrations are required? 3. DESIGN THE ARCHITECTURE: - What is the system structure? - How do components interact? - What are the data flows? - What technologies are appropriate? 4. DECOMPOSE INTO TASKS: - What are the logical work packages? - What are the dependencies between tasks? - What can be done in parallel? - What is the effort estimation? 5. IDENTIFY RISKS: - What could go wrong technically? - What are the performance concerns? - What are the security implications? - How can risks be mitigated? CRITICAL: Epic must be technically feasible and properly scoped - Ensure tasks are independent where possible - Estimate effort realistically - Identify clear acceptance criteria - Plan for testing and documentation {{#if existing_code}} Current system implementation {{existing_code}} {{/if}} {{#if example}} Reference epic structure {{example}} {{/if}} All PRD requirements addressed Technical approach is sound Tasks are properly scoped Dependencies are clear Effort estimates are realistic Risks are identified Acceptance criteria defined Integration points specified Data model designed (if applicable) API specification complete (if applicable)