epic

Command: /epic [epic description | slug | continue | next]

Runtime ownership note: Epic workflow semantics and state belong to the shared canon. This command is currently a Claude adapter surface while epic runtime behavior converges on the same shared ownership model as the rest of Spec-Flow.

CRITICAL ARCHITECTURE (v7.0 - Domain Memory v2):

This orchestrator is ultra-lightweight. You MUST:

1. Read state from disk (state.yaml, interaction-state.yaml, domain-memory.yaml)
2. Spawn isolated phase agents via Task tool - NEVER execute phases inline
3. Handle user Q&A when agents return questions
4. Update state.yaml after each phase
5. NEVER carry implementation details in your context

Key Difference from /feature:

• Epic creates sprint-level domain-memory.yaml files for parallel execution
• Implementation spawns multiple workers across sprints simultaneously
• More sophisticated dependency tracking between sprints

Benefits: Unlimited epic complexity, 3-5x faster delivery via parallelism, observable progress, resumable at any point.

Project State: !test -d docs/project && echo "initialized" || echo "missing"

Git Configuration:

• Remote: !git remote -v 2>/dev/null | head -1 | grep -q origin && echo "configured" || echo "none"
• Current branch: !git branch --show-current 2>/dev/null || echo "none"
• Staging workflow: !test -f .github/workflows/deploy-staging.yml && echo "present" || echo "missing"

Epic Workspace: !ls -d epics/*/ 2>/dev/null | head -3 || echo "none"

Workflow State: @epics/*/state.yaml

Planning Depth Preference: !bash .spec-flow/scripts/utils/load-preferences.sh --key "planning.auto_deep_mode" --default "false" 2>/dev/null || echo "false"

Epic Trigger for Deep Planning: !bash .spec-flow/scripts/utils/load-preferences.sh --key "planning.deep_planning_triggers.epic_features" --default "true" 2>/dev/null || echo "true"

Auto-ship preference: !bash .spec-flow/scripts/utils/load-preferences.sh --key "deployment.auto_ship" --default "false" 2>/dev/null || echo "false"

Auto-merge preference: !bash .spec-flow/scripts/utils/load-preferences.sh --key "deployment.auto_merge" --default "false" 2>/dev/null || echo "false"

Auto-finalize preference: !bash .spec-flow/scripts/utils/load-preferences.sh --key "deployment.auto_finalize" --default "true" 2>/dev/null || echo "true"

Studio context (multi-agent isolation): !bash .spec-flow/scripts/bash/worktree-context.sh studio-detect 2>/dev/null || echo ""

Worktree context: !bash .spec-flow/scripts/bash/worktree-context.sh info 2>/dev/null || echo '{"is_worktree": false}'

<planning_depth>

Planning Depth Mode for Epics

NOTE: Epics automatically trigger ultrathink/deep planning by default via deep_planning_triggers.epic_features: true.

Flags in $ARGUMENTS:

• --deep → Explicitly force ultrathink (redundant for epics, but explicit)
• --auto → Use preferences AND continue through ship→finalize without stopping
• Neither → Interactive mode, still uses deep planning for epics

Epic-specific benefits of ultrathink:

• Assumption questioning across multiple sprints
• Codebase soul analysis informs sprint boundaries
• Minimum viable architecture prevents over-engineering
• Design alternatives help sprint prioritization

State tracking:

# In epics/NNN-slug/state.yaml
planning:
  mode: deep
  ultrathink_enabled: true
  triggered_by: epic_features  # or explicit_flag

</planning_depth>

<auto_mode>