epic-analyze

description: Analyze epic plan, tech spec, and task breakdown for consistency and completeness before implementation.

The user input to you can be provided directly by the agent or as a command argument - you MUST consider it before proceeding with the prompt (if not empty).

User input:

$ARGUMENTS

Validate epic planning artifacts to identify issues before story implementation begins.

1. •

   Load epic artifacts:

   • •epic.md (specification)
   • •epic-tech-spec.md (technical design with embedded research)
   • •epic-breakdown.md (story mapping)
   • •Related scan reports (epic-codebase-scan*.md)
   • •Project-level PRD and constraints
   • •If core files missing: ERROR "Complete epic planning first"

   Note: Research is now embedded in epic-tech-spec.md - no separate research.md to validate.

2. •

   Multi-aspect analysis:

   A. Requirement Coverage

   • •All user stories have tasks?
   • •All acceptance criteria addressable?
   • •Technical requirements mapped?
   • •Edge cases handled?

   B. Technical Coherence

   • •Architecture supports all stories?
   • •Technology choices consistent?
   • •Integration points defined?
   • •Performance strategy adequate?

   C. Task Completeness

   • •All stories broken into tasks?
   • •Dependencies correctly mapped?
   • •Parallel opportunities identified?
   • •Effort estimates reasonable?

   D. Risk Assessment

   • •Technical risks addressed?
   • •Dependencies manageable?
   • •Fallback plans exist?
   • •Critical path reasonable?

   E. Quality Coverage

   • •Test strategy comprehensive?
   • •Documentation planned?
   • •Security addressed?
   • •Performance validated?
3. •

   Deep analysis checks:

   Story Traceability Matrix

   code

   | User Story | Tech Spec Section | Task ID | Test Coverage |
   |------------|------------------|---------|---------------|
   | Story 1.1 | Section 4.1 | S004 | Unit, Integration |
   

   Dependency Analysis

   • •Circular dependencies?
   • •External blockers?
   • •Critical path too long?
   • •Parallel opportunities missed?

   Technical Debt Assessment

   • •Shortcuts taken?
   • •Future refactoring needed?
   • •Technical compromises?
4. •

   Generate analysis report:

   CRITICAL: Load and follow the template exactly:

   code

   .speck/templates/epic/epic-analysis-report-template.md
   

   Write output to: [EPIC_DIR]/epic-analysis-report.md

5. •

   Generate fix suggestions:

   code

   ## Quick Fixes
   
   For missing task:
   Add to epic-breakdown.md Phase 2:
   - [ ] S006 [Story 2.1 implementation]
   
   For circular dependency:
   Refactor S006 to not depend on S005
   

6. •

   Save as [EPIC_DIR]/epic-analysis-report.md

7. •

   Output summary:

   code

   ✅ Epic Analysis Complete!
   
   Status: [Ready/Issues Found]
   
   Coverage:
   - Stories with tasks: [X]%
   - Technical coverage: [Y]%
   - Risk mitigation: [Z]%
   
   Critical Issues: [Count]
   Warnings: [Count]
   
   [If Ready]:
   Next: Begin implementation with Phase 1 stories
   
   [If Issues]:
   Fix critical issues then re-run /epic-analyze
   
   Full report: epic-analysis-report.md
   

This ensures epic plan is solid before story work begins.