/ready
Validate completed work, promote it, and continue to inspection autonomously.
/ready receives a delivery context from /work, or in standalone mode asks
for the plan, item, and exact request. It verifies the complete delivery
against the approved plan, returns concrete gaps to /work, and promotes
passing work for inspection.
How /ready promotes completed work
Readiness loop
01 · AutonomousVerify deliveryRun planned validation and compare the complete branch with the approved outcome.
Delivery gaps/workCreate and execute corrective todos.Corrected work02 · AutonomousPromote requestPush the branch, publish the complete plan, and mark the request ready for review.
Workflow/inspectInspect the exact promoted request snapshot./ready runs only the validation defined by the plan. It checks delivery
completeness, but does not select a specialist or perform an independent code
review.
What /ready does
| 1 | Verify | Require a terminal plan, completed work, and one clean branch that is not behind or diverged. |
|---|---|---|
| 2 | Match | Run only planned validation and compare the complete branch diff with the Objective and Expected Outcome. |
| 3 | Repair | Return each concrete gap to /work as a corrective todo, then verify the corrected delivery again. |
| 4 | Promote | Push when needed, use the complete plan as the request description, mark the request ready, and continue to inspection. |
| 5 | Inspect | After observing every required request update, continue automatically to /inspect. |