rpi-quick

RPI

Goal

Coordinate one task through evidence, planning, execution, review, and explicit follow-up without duplicating the phase skills' detailed responsibilities.

Flow

1. Assess research readiness from caller-supplied research, task details, decisions, and plan inputs.
   1. Activate rpi-research only when evidence is missing, stale, contradictory, insufficient for planning, or when complexity, uncertainty, dependencies, risk, or a decision-critical question warrants investigation. Record Research disposition executed and consume the primary artifact's Planning Readiness.
   2. When evidence is adequate, record disposition reused or satisfied-and-skipped with the evidence that supports it.
   3. Apply the rpi-research continuation contract. Continue to Plan without another stage-start command only when either an executed Research primary artifact records Planning Readiness Ready, or reused or satisfied-and-skipped evidence is adequate, and all applicable gates pass, blockers clear, and required confirmations are explicit.
   4. When Research is Blocked, Needs clarification, or Not ready, or another transition requirement is not met, stop in Research and record the blocker or next action.
2. Run rpi-plan to create or revise the ordinary Markdown plan and phase details. Its rpi-plan-critique gate is internal to planning and returns its disposition to the planning parent.
3. Run rpi-implement for approved Pxx and Pxx-Txx work. Consume its return, including completed and remaining markers, validation coverage, blockers, plan and detail updates, follow-up items, and readiness or the reason work is awaiting a significant or divergent user decision.
4. Run rpi-review once after Implementation returns and no affected work awaits a user decision. Compare the current plan, details, critique, descriptive changes record, and validation evidence. Record execution status separately from outcome.
5. Follow-up: route defects, decision gaps, research gaps, and residual work to their correct next destination.