rpilisted

# $rpi — Full RPI Lifecycle Orchestrator > **Quick Ref:** One command, full lifecycle. `$discovery` → `$crank` → `$validation`. Thin wrapper that delegates to phase orchestrators. **YOU MUST EXECUTE THIS WORKFLOW. Do not just describe it.** **THREE-PHASE RULE + FULLY AUTONOMOUS.** Read `references/autonomous-execution.md` — it defines the mandatory 3-phase lifecycle, autonomous execution rules, anti-patterns, and phase completion logging. Unless `--interactive` is set, RPI runs hands-free. Do NOT stop after Phase 2. Do NOT ask the user anything between phases. ## Codex Lifecycle Guard When this skill runs in Codex hookless mode (`CODEX_THREAD_ID` is set or `CODEX_INTERNAL_ORIGINATOR_OVERRIDE` is `Codex Desktop`), ensure startup context before phase orchestration: ```bash ao codex ensure-start 2>/dev/null || true ``` `ao codex ensure-start` is the single startup guard for Codex skills. It records startup once per thread and skips duplicate startup automatically. Let `$validation`, `$post-mortem`, or `$handoff` own the hookless closeout path via `ao codex ensure-stop`. ## Objective Scope Guard `$rpi` owns one lifecycle objective from discovery through validation. 1. Keep one objective spine across phases: - if discovery or resume state yields an `epic_id`, preserve that `epic_id` - otherwise preserve the original goal plus execution-packet objective 2. Never replace the current objective with a child issue or one ready slice surfaced by `bd ready`, `bd show`, or