← ClaudeAtlas

rpi-workflowlisted

Research-Plan-Implement workflow with Codex peer review. Use when the user says /rpi, asks to start a research-plan-implement cycle, wants Codex review on a plan, or needs to create research docs, plans, or implementation reports following the RPI protocol.
shubham0704/claude-skills · ★ 1 · AI & Automation · score 77
Install: claude install-skill shubham0704/claude-skills
# RPI Workflow: Research -> Plan -> Implement A structured workflow for complex engineering tasks with Codex architectural review. ## When to Invoke - User says `/rpi` or "start RPI" - User wants structured research before implementation - User wants Codex to review a plan - User needs to create research docs or implementation plans ## File Structure All artifacts go in `docs/` at the project root: ``` docs/ ├── research/ │ └── YYYY-MM-DD-topic.md # Research findings └── plans/ ├── PLAN-<repo>-<task>.md # Claude creates ├── FEEDBACK-<repo>-<task>.md # Codex creates ├── IMPL-<repo>-<task>.md # Claude creates after implementation └── VALIDATION-<repo>-<task>.md # Codex creates (optional) ``` ## Workflow Steps ### Step 1: Research Phase Launch parallel Explore agents to gather codebase understanding: ``` Task(subagent_type="Explore", prompt="Research how X works...") Task(subagent_type="Explore", prompt="Research how Y connects to Z...") ``` Save findings to `docs/research/YYYY-MM-DD-topic.md` using the research template. For the template structure, see [TEMPLATES.md](TEMPLATES.md). ### Step 2: Plan Phase Create `docs/plans/PLAN-<repo>-<task>.md` with: - Goal (1-2 sentences) - Key Files (`path:line` references) - Problem (what's broken/missing) - Proposed Solution (phased, with file-level changes) - Success Criteria (checkboxes) - Risks (numbered) - Questions for Review (for Codex) ### Step 3: Codex Review Run from the **project