01 ▸ Workflow Position
User Request (Complex)
│
▼
┌─────────────────────────────┐
│ Clarification (9-15 points)│
└──────────────┬──────────────┘
│
▼
┌─────────────────────────────┐
│ Milestone Planning (ACTIVE)│
│ 5 Parallel Reviews + DAG │
└──────────────┬──────────────┘
│
▼
┌─────────────────────────────┐
│ Long Run │
│ Per-Milestone Execution │
└─────────────────────────────┘
02 ▸ When to use?
Used when Clarification results in a Complex (9-15 points) verdict, or when a large-scale task spanning multiple days is required.
Key Triggers
- When
"divide into milestones" or "ultraplan" commands are used
- When the Long Run harness requests milestone decomposition
- When the task exceeds the scope of a one-time plan (plan-crafting)
03 ▸ How it works?
Core Principle: 5 reviewers criticize the problem from their own expert perspectives (Feasibility, Architecture, Risk, Dependency, User Value) while remaining information isolated from each other.
Execution Steps
- Problem Framing: Write a Problem Brief including goals, scope, and constraints.
- Parallel Dispatch: Launch 5 reviewer agents simultaneously (preventing cross-contamination).
- Synthesis: Compare review results to resolve conflicts and synthesize the Milestone DAG.
- DAG Validation: Verify circular dependencies and file conflicts.
- Integration Milestone: Automatically add a final integration verification milestone.
04 ▸ Milestone Count Guard
A count of 3~7 milestones is recommended. A warning is displayed if it exceeds 7, and project splitting should be considered if it exceeds 10.
05 ▸ Hard Gates
- All reviewers must run in parallel (no sequential execution).
- Maintain Information Isolation between reviewers (they cannot see each other's results).
- Every milestone must have measurable success criteria.
- Dependency structure must be a DAG (no cycles).
- Reviewer outputs must be delivered verbatim to the synthesis agent.