Autopilot

$ralplan -> $ralph -> $code-review

If $code-review is not clean, Autopilot returns to $ralplan with the review findings as the next planning input, then continues again through $ralph and $code-review until the review is clean or a hard blocker is reported.

1. Phase ralplan — consensus planning gate

   • Ground the task with pre-context intake.
   • Run or resume $ralplan to produce/update PRD and test-spec artifacts.
   • When returning from a non-clean review, include return_to_ralplan_reason and the review findings as first-class planning input.
   • Required handoff artifact: an approved plan/test spec suitable for $ralph.

2. Phase ralph — implementation + verification loop

   • Run $ralph from the approved ralplan artifacts.
   • Ralph owns implementation, tests, build/lint/typecheck evidence, deslop where applicable, and architect verification.
   • Required handoff artifact: implementation evidence and changed-file summary suitable for $code-review.

3. Phase code-review — merge-readiness gate

   • Run $code-review on the diff/artifacts produced by $ralph.
   • A clean review means final recommendation APPROVE with architectural status CLEAR.
   • COMMENT, REQUEST CHANGES, any architectural WATCH/BLOCK, or any unresolved finding is not clean.
   • If not clean, increment the review cycle, persist review_verdict, set return_to_ralplan_reason, and transition back to Phase ralplan.

The only normal terminal state is complete after a clean code review. Cancellation, blocked credentials, unrecoverable repeated failures, or explicit user stop may terminate earlier with preserved state.

Before Phase ralplan starts or resumes:

1. Derive a task slug from the request.
2. Reuse the latest relevant .omx/context/{slug}-*.md snapshot when available.
3. If none exists, create .omx/context/{slug}-{timestamp}.md (UTC YYYYMMDDTHHMMSSZ) with:
   • task statement
   • desired outcome
   • known facts/evidence
   • constraints
   • unknowns/open questions
   • likely codebase touchpoints
4. If ambiguity remains high, run explore first for brownfield facts, then run the Socratic $deep-interview --quick <task> before $ralplan.
5. Carry the snapshot path in Autopilot state and all handoff artifacts. </Pre-context Intake>

Required fields:

{
  "mode": "autopilot",
  "active": true,
  "current_phase": "ralplan",
  "iteration": 1,
  "review_cycle": 0,
  "max_iterations": 10,
  "phase_cycle": ["ralplan", "ralph", "code-review"],
  "handoff_artifacts": {
    "context_snapshot_path": ".omx/context/<slug>-<timestamp>.md",
    "ralplan": null,
    "ralph": null,
    "code_review": null
  },
  "review_verdict": null,
  "return_to_ralplan_reason": null
}

• On start: state_write({mode:"autopilot", active:true, current_phase:"ralplan", iteration:1, review_cycle:0, state:{phase_cycle:["ralplan","ralph","code-review"], handoff_artifacts:{context_snapshot_path, ralplan:null, ralph:null, code_review:null}, review_verdict:null, return_to_ralplan_reason:null}})
• On ralplan -> ralph: set current_phase:"ralph", persist the plan/test-spec paths under handoff_artifacts.ralplan.
• On ralph -> code-review: set current_phase:"code-review", persist implementation/test evidence under handoff_artifacts.ralph.
• On clean review: set active:false, current_phase:"complete", persist review_verdict:{recommendation:"APPROVE", architectural_status:"CLEAR", clean:true} and completed_at.
• On non-clean review: increment iteration and review_cycle, set current_phase:"ralplan", persist review_verdict:{..., clean:false}, persist handoff_artifacts.code_review, and set return_to_ralplan_reason to a concise review-driven reason.
• On cancellation: run $cancel; preserve progress for resume rather than deleting handoff artifacts.

Do not restart discovery or discard handoff artifacts on continuation.

ralplan -> ralph -> code-review

Pipeline state should use current_phase values that match the same phase names (ralplan, ralph, code-review, complete, failed) and should carry iteration, review_cycle, handoff_artifacts, review_verdict, and return_to_ralplan_reason alongside stage results.