rpi/research
Researches and analyses whether a feature is viable, as a GO or NO-GO decision gate.
- Kind
- Prompt
- Works with
- Claude Code
- Source
- shanraisshan/claude-code-best-practice @ 6d0844baf620
- Path
- development-workflows/rpi/.claude/commands/rpi/research.md
- License
- MIT
- Jobs
- Planning
InstallCopy it from the source repository, or sign in and let the assistant adapt it for your project.
## User Input
```text
$ARGUMENTS
```
You **MUST** parse the user input to extract the feature slug (the folder name in `rpi/`).
**Expected Input Format**: `rpi/{feature-slug}/REQUEST.md`
## Purpose
This command performs comprehensive research and analysis of feature requests **before** the planning phase begins. It acts as a critical GO/NO-GO gate to determine whether a feature idea should proceed to detailed planning.
**Key Objectives**:
- Assess product-market fit and user value
- Evaluate technical feasibility and complexity
- Identify risks and potential blockers
- Determine the right approach (build, buy, partner, or decline)
- Make go/no-go recommendation with clear rationale
**Prerequisites**:
- Feature folder exists at `rpi/{feature-slug}/`
- Feature request file exists at `rpi/{feature-slug}/REQUEST.md`
**Output Location**: `rpi/{feature-slug}/research/RESEARCH.md`
**This is Step 2 of the RPI Workflow** (after initial feature description in Step 1).
## Outline
1. **Load Context**: Read feature description from `rpi/{feature-slug}/` and project constitution (if exists)
2. **Parse Feature Request**: Use requirement-parser agent to extract structured requirements
…