01 ▸ Workflow Position
Milestone Planning
│
▼
┌─────────────────────────────┐
│ Long Run (ACTIVE) │
│ Per-Milestone Execution │
└──────────────┬──────────────┘
│
▼
Review Work
02 ▸ When to use?
Immediately after Milestone Planning is complete, or when large-scale refactoring/feature development spanning multiple days is required.
Key Triggers
"long run""execute milestones"- Input: Locked Milestone DAG
03 ▸ How it works?
Core Principle: Every milestone undergoes an independent plan→run→review cycle. A failed milestone blocks all subsequent ones.
Execution Steps
- Sequential Milestone Execution: Perform planning, execution, and verification for each milestone and save checkpoints.
- Retry Escalation: Attempt up to 3 retries in the order: Re-run → Re-plan → Stop (Persistent Counter).
- Parallel Milestones (worktree): Milestones without dependencies are executed simultaneously in separate git worktrees.
- Cross-Milestone Integration Check: Detect interference between milestones after each completion.
- Final E2E Gate: Perform final verification after completion and clean up code with Simplify.
04 ▸ Durable Design
| Feature | Description |
|---|
| Disk Checkpoint | Record all status in state.md — Crash survival |
| Recovery Protocol | Resume from the last checkpoint in interrupted sessions |
| Rate limit | Align with Claude Code's built-in retries |
| Context Window | Automatic compression and state separation for long-term conversations |
05 ▸ Hard Gates
Mandatory Rules
- A failed milestone must immediately block the execution of subsequent milestones.
- Retry counters must be persistent, maintained even if the session is interrupted.
- Pre-verify that there are no file conflicts between each worktree during parallel execution.
- All state changes must be immediately reflected in
state.md on disk.