Workflows · WorkflowEveryday codingResearch & AnalysisReviewed

rpi-workflow

Research, plan and implement a feature in three phases, with a GO or NO-GO gate and validation gates along the way.

Kind: Workflow
Works with: Claude Code
Source: shanraisshan/claude-code-best-practice @ 6d0844baf620
Path: development-workflows/rpi/rpi-workflow.md
License: MIT
Jobs: Planning, Implementation

InstallCopy it from the source repository, or sign in and let the assistant adapt it for your project.

# RPI Workflow

**RPI** = **R**esearch → **P**lan → **I**mplement

A systematic development workflow with validation gates at each phase. Prevents wasted effort on non-viable features and ensures comprehensive documentation.

<table width="100%">
<tr>
<td><a href="../../">← Back to Claude Code Best Practice</a></td>
<td align="right"><img src="../../!/claude-jumping.svg" alt="Claude" width="60" /></td>
</tr>
</table>

---

## Overview

![RPI Workflow](rpi-workflow.svg)

---

## Installation

Copy the `.claude` folder (containing `agents/` and `commands/rpi/`) to your repository root, then create the `rpi/plans` directory.

---

## Example Workflow

### Feature: User Authentication

**Step 1: Describe**
```
User: "Add OAuth2 authentication with Google and GitHub providers"

1. Claude generates plan
   → Output: rpi/plans/oauth2-authentication.md
2. Create feature folder: rpi/oauth2-authentication/
3. Copy the plan into the feature folder
4. Rename the plan to REQUEST.md
   → Final: rpi/oauth2-authentication/REQUEST.md
```

**Step 2: Research**
```bash
/rpi:research rpi/oauth2-authentication/REQUEST.md
```
Output:
- `research/RESEARCH.md` with analysis
…