01 ▸ Workflow Position
Plan Crafting (Plan Complete)
│
▼
┌─────────────────────────────┐
│ Run Plan (ACTIVE) │
│ Worker-Validator Loop │
└──────────────┬──────────────┘
│
▼
Review Work (Final Independent Verification)
02 ▸ When to use?
Immediately after Plan Crafting is complete, or when you need to implement an already written plan document into actual code.
Key Triggers
"execute the plan""run plan""start implementing the drafted plan"
03 ▸ How it works?
Core Principle: The Validator never looks at the Worker's code. It independently verifies that the output is correct based only on the plan's goals and acceptance criteria.
Step-by-step Execution Process
- Discover Verification Infrastructure: Identify available test runners, linters, and agent skills in the current environment.
- Pre-implementation Review: Final check for potential file conflicts or dependency order errors before implementation.
- Worker-Validator Loop: As the Worker performs tasks, the Validator independently reviews the output.
- E2E Verification Gate: Once all individual steps are complete, confirm the integrated behavior of the entire system.
04 ▸ Parallel Execution Rules
| Condition | Execution Mode |
|---|
| No file overlap + no dependencies | Parallel allowed |
| Modifying the same file | Serial — perform after previous is done |
| Output of Task A is Input of Task B | Serial — follow sequential dependencies |
05 ▸ Hard Gates
- 3-Failure Limit: If verification fails 3 consecutive times on the same step, stop immediately and escalate to the user.
- Information Isolation: The Validator does not see the Worker's implementation logs; it only compares against planned acceptance criteria.
- No Completion without Verification: Every code change must pass automated tests or a clear verification procedure.