rpi-workflow
Skill2 starsChanged 6 months agoMITView on GitHub
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.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- matt-riley/agent-skillstheir own version, first seen Nov 15, 2026
- apps-ser/claude-skillstheir own version, first seen Jun 30, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- matt-riley/agent-skills★ 3same name
- apps-ser/claude-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 5 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
All artifacts go in docs/ at the project root:
- Distinctive: line 59
Run from the project root:
- Very specific: line 66
Always use --skip-git-repo-check for non-git repos
- Very specific: line 72
Read docs/plans/FEEDBACK-<repo>-<task>.md and present key findings to the user:
- Distinctive: line 96
Research first: Never plan without understanding the codebase
- Distinctive: line 97
Parallel agents: Use multiple Explore agents simultaneously
- Very specific: line 98
Compact findings: Use file:line references, not full code dumps
- Distinctive: line 99
Questions for Codex: Always include 3-5 specific architectural questions
- Distinctive: line 100
Parity checks: Before deleting old code, run side-by-side comparisons
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
RPI Workflow: Research -> Plan -> Implement
A structured workflow for complex engineering tasks with Codex architectural review.
When to Invoke
- User says
/rpior "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.
Step 2: Plan Phase
Create docs/plans/PLAN-<repo>-<task>.md with:
- Goal (1-2 sentences)
- Key Files (
path:linereferences) - 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 root:
codex exec --skip-git-repo-check "Read docs/plans/PLAN-<repo>-<task>.md and provide architectural feedback. Review the proposed solution, identify risks, suggest improvements. Write your feedback to docs/plans/FEEDBACK-<repo>-<task>.md"Notes:
- Always use
--skip-git-repo-checkfor non-git repos - No
--quietflag exists - Codex writes feedback autonomously to the FEEDBACK file
Step 4: Read & Incorporate Feedback
Read docs/plans/FEEDBACK-<repo>-<task>.md and present key findings to the user:
- Executive assessment
- Missing edge cases
- Better abstractions suggested
- Risks not identified
- Phase reordering suggestions
- Actionable recommendations
Step 5: Implement
Make the changes. Create docs/plans/IMPL-<repo>-<task>.md documenting:
- What was actually changed (with
path:linerefs) - Deviations from plan and why
- Test results
- Remaining work
Step 6: Validate (Optional)
codex exec --skip-git-repo-check "Read docs/plans/IMPL-<repo>-<task>.md and validate the implementation. Check if success criteria are met, identify any issues. Write your validation to docs/plans/VALIDATION-<repo>-<task>.md"Guidelines
- Research first: Never plan without understanding the codebase
- Parallel agents: Use multiple Explore agents simultaneously
- Compact findings: Use
file:linereferences, not full code dumps - Questions for Codex: Always include 3-5 specific architectural questions
- Parity checks: Before deleting old code, run side-by-side comparisons
- Phase boundaries: Each phase should be independently mergeable
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

