/rpi - Full Lifecycle Orchestrator

Quick ref: /discovery -> /crank -> /validation, then report.

Execute this workflow. Do not only describe it. RPI is autonomous unless --interactive is set. The user touchpoint is after validation, or after a real blocked state exhausts retries. Read references/autonomous-execution.md when you need the full autonomy contract.

When an external executor fails but the code surface may still be valid, read references/codex-executor.md and recover through Codex direct checks before declaring a source-level regression.

Loop position

/rpi is the orchestrator across every move of the operating loop: BDD intent → vertical slices → conflict-free wave → bead acceptance → evidence + learning capture. It delegates each move to the skill that owns it (/discovery, /plan, /crank, /validation, /forge//retro), and enforces three loop-level invariants: