Three-Phase Workflow
The prepare → execute → validate cycle that every task follows.
Why three phases?
Agents do better work when they slow down at the right moments. The three-phase workflow keeps them from skipping context, widening scope, or claiming completion without evidence.
Phase 1 — Prepare
Before changing anything, the agent should:
- Read the action item.
- Adopt the right role.
- Check prior work and related knowledge.
- Identify what evidence will prove the work is complete.
- Keep the scope narrow enough to review.
This is the "do the homework" phase. It prevents agents from solving the wrong problem quickly.
Phase 2 — Execute
The agent does the work inside the agreed scope. A good execution pass respects existing patterns, avoids unrelated cleanup, and records anything that could not be finished.
For copy, this means matching the product truth. For code, it means reading before writing. For operations, it means using the current board and runtime state instead of stale notes.
Phase 3 — Validate
Validation turns "I think it is done" into evidence. Depending on the task, proof may include:
- Build or test output.
- Runtime proof.
- Link checks.
- Screenshots.
- A Knowledge Item.
- A deliverable.
- A clear note about remaining risk.
Only after validation should the item move to review.
Next: Completion Gate, Deliverables, and Knowledge Items.