epic-outline

description: Analyze epic specification to identify technical decisions and research needs before creating tech spec.

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

Create a technical outline that identifies key architectural decisions and research areas needed for epic implementation.

1. •

   Load epic context:

   • •Find epic.md in current or parent directory
   • •Load project PRD.md for technical constraints
   • •Check for existing epic-outline.md
   • •Review other epics for integration patterns
   • •If no epic.md: ERROR "Run /epic-specify first"
2. •

   Technical decision categories:

   Architecture Decisions

   • •Component structure approach
   • •State management strategy
   • •API design patterns
   • •Data flow architecture

   Technology Choices

   • •Libraries/frameworks needed
   • •Build vs buy decisions
   • •Integration approaches
   • •Testing strategies

   Implementation Patterns

   • •Error handling approach
   • •Logging/monitoring strategy
   • •Security implementation
   • •Performance optimizations
3. •

   Research need identification:

   • •Technology evaluation needs
   • •Best practice research
   • •Integration documentation
   • •Performance benchmarks needed
4. •

   Generate epic outline:

   CRITICAL: Load and follow the template exactly:

   code

   .speck/templates/epic/outline-template.md
   

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

5. •

   Save as [EPIC_DIR]/epic-outline.md

6. •

   Output summary:

   code

   ✅ Epic Technical Outline Complete!
   
   Key Decisions Identified: [X]
   Research Areas: [Y] critical, [Z] important
   
   Next Steps:
   1. Use the just-in-time research pattern (`.cursor/skills/just-in-time-research/SKILL.md`)
      to address the outline’s highest-priority questions (web search first; generate a deep
      research prompt only if needed)
   2. Then: /epic-plan