en un clic
structured-rpi
// Enhanced Research-Plan-Implement workflow with structured phase gates. Use when tackling complex tasks that benefit from a phased approach with user checkpoints.
// Enhanced Research-Plan-Implement workflow with structured phase gates. Use when tackling complex tasks that benefit from a phased approach with user checkpoints.
Setup guide for essential MCP servers. Use when configuring MCP servers or when user asks about search, SQLite, or MCP management.
Query Claude Code session analytics from ccrecall database. Use when user asks about token usage, session history, or wants to analyze their Claude Code usage patterns.
High-leverage prompts that challenge Claude's defaults. Use for "grill me", "prove it works", "scrap this", "what would 10x engineer do", "find ways this fails".
Maintain CLAUDE.md files effectively. Use when adding lessons learned, updating conventions, or restructuring project instructions.
Multi-agent orchestration patterns for Claude Code team mode. Use when coordinating teammates, decomposing complex tasks, or managing shared task lists.
Terminal setup for Claude Code. Use for Ghostty config, statusline customization, voice dictation, tmux worktrees.
| name | structured-rpi |
| description | Enhanced Research-Plan-Implement workflow with structured phase gates. Use when tackling complex tasks that benefit from a phased approach with user checkpoints. |
A 6-phase workflow that decomposes complex tasks into gated stages, each producing a markdown artifact the user approves before advancing.
Use structured RPI to refactor the authentication module.
The workflow walks through six phases sequentially. Each phase produces a concise markdown artifact. You must get user approval before moving to the next phase.
| # | Phase | Artifact | Purpose |
|---|---|---|---|
| 1 | Questions | Clarifying questions list | Surface unknowns and ambiguity |
| 2 | Research | Findings summary | Gather context from code and docs |
| 3 | Design Discussion | Design options + tradeoffs | Explore approaches with the user |
| 4 | Structure Outline | Component/file outline | Agree on shape before details |
| 5 | Plan | Implementation plan (Plan tool) | Concrete steps with acceptance criteria |
| 6 | Implement | Working code + verification | Execute the plan |
After each artifact, present:
Phase N complete. Ready to proceed to Phase N+1 (Name)?
Options: [approve] [request changes] [skip to phase N+X] [abort]
| Situation | Use Structured RPI? |
|---|---|
| Complex refactor spanning multiple files | Yes |
| New feature with unclear requirements | Yes |
| Bug fix with known cause | No — just fix it |
| One-file change | No — overkill |
| User says "plan this out" or "let's think through this" | Yes |