executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
pipelineConfigurable pipeline orchestrator for sequencing stages
Independent GitHub snapshot · Automated classification · Original documentation governs
$pipeline is the configurable pipeline orchestrator for OMX. It sequences stages
through a uniform PipelineStage interface, with state persistence and resume support.
The default Autopilot pipeline sequences:
deep-interview -> ralplan -> ultragoal (+ team if needed) -> code-review -> ultraqa
$team is conditional: use it only inside an active Ultragoal story when independent lanes or broad verification make coordinated parallel execution useful. Explicit legacy Ralph pipelines remain available through custom stages, but Ralph is not the advertised default Autopilot loop.
Pipeline parameters are configurable per run:
| Parameter | Default | Description |
|---|---|---|
maxRalphIterations | 10 | Quality-gate retry ceiling; legacy option name retained for compatibility |
workerCount | 2 | Number of Codex CLI team workers |
agentType | executor | Agent type for team workers |
Every stage implements the PipelineStage interface:
interface PipelineStage {
readonly name: string;
run(ctx: StageContext): Promise<StageResult>;
canSkip?(ctx: StageContext): boolean;
}
Stages receive a StageContext with accumulated artifacts from prior stages and
return a StageResult with status, artifacts, and duration.
prd-*.md and test-spec-*.md planning artifacts already exist and durable consensus evidence records Architect approval followed by Critic approval. Plan/test-spec files alone are not consensus evidence. If either review is missing, blocked, out of order, or non-approving, the stage remains in ralplan or fails with an explicit blocker/max-iteration outcome instead of progressing to execution. Carries any deep-interview-*.md spec paths forward for traceability..omx/ultragoal ledgers. Launch $team only from inside an Ultragoal story when parallel lanes are warranted.Pipeline state persists via the ModeState system at .omx/state/pipeline-state.json.
The HUD renders pipeline phase automatically. Resume is supported from the last incomplete stage.
omx state write --input '{"mode":"pipeline","active":true,"current_phase":"stage:ralplan"}' --jsonomx state write --input '{"mode":"pipeline","current_phase":"stage:<name>"}' --jsonomx state write --input '{"mode":"pipeline","active":false,"current_phase":"complete"}' --jsonimport {
runPipeline,
createAutopilotPipelineConfig,
createDeepInterviewStage,
createRalplanStage,
createUltragoalStage,
createCodeReviewStage,
createUltraqaStage,
} from './pipeline/index.js';
const config = createAutopilotPipelineConfig('build feature X', {
stages: [
createDeepInterviewStage(),
createRalplanStage(),
createUltragoalStage(),
createCodeReviewStage(),
createUltraqaStage(),
],
});
const result = await runPipeline(config);