claude

rpi

RPI pipeline: research, plan, implement — a streamlined 3-phase workflow for feature development

2 on GitHubby Ron Sanzoneupdated 5 months ago
/

Plugin rpi from marketplace context-engineering-workflows in ronsanzone/context-engineering-workflows. Commands read from the repo's manifest — 1 month ago.

What it installs

Skills (3)

  • rpi-implement

    Use when you have a plan from /rpi-plan and want to execute it. Dispatches a fresh subagent per task with two-stage review (spec compliance → code quality), then runs a baked-in end-of-implementation audit that re-runs success criteria, checks the diff against the plan, and dispatches /quick-review

  • rpi-plan

    Use after /rpi-research when you want an interactive, gated plan-creation flow. Interactive: presents understanding, design options, phase outline, then draft — each gated on user approval.

  • rpi-research

    Use when starting the RPI flow and you want to deeply understand a question, system, or feature by reading the codebase before planning.

Subagents (3)

  • codebase-analyzer

    Produces a structured "how it works" writeup of existing code, with file:line citations on every claim and optional mermaid flow diagrams. Use when you need a durable technical artifact (data flow, control flow, integration points) — not a quick exploratory answer. Prefer over `Explore` when the res

  • codebase-locator

    Returns a categorized file-location inventory for a feature (implementation / tests / config / types / docs) — paths only, no analysis of contents. Prefer over `Explore` when you're planning changes and need to know WHERE code lives, not what it does. Use whenever you'd otherwise run grep/glob/ls mo

  • codebase-pattern-finder

    Returns 3–4 ready-to-copy code snippets (10–30 lines each, with file:line refs and matching tests) showing how a pattern is implemented in this codebase. Use when you're about to write new code that should match existing conventions. Prefer over `Explore` when you need concrete template examples to

View source on GitHub

More from ronsanzone/context-engineering-workflows

All 2 plugins →

dw

claude

Deep-work pipeline: 6-phase structured workflow separating research from solutioning

6 skills · 3 agents

2

Similar plugins

5 skills + 35 modes + Material Passport pipeline. Includes v3.6.7 cross-model audit gate and v3.6.8 generator-evaluator contract.

5 skills · 16 commands · 4 agents · hooks

Imbad0202/academic-research-skills 56,698

conductor

claudecodex

Context-Driven Development plugin that transforms Claude Code into a project management tool with structured workflow: Context → Spec & Plan → Implement

3 skills · 6 commands · 1 agent

wshobson/agents 42,461

openseo

claudecodex

Without good data, your agent gives generic advice. Keyword research, competitor research, backlinks, and site audits. All for $10/month.

12 skills · 1 MCP server

every-app/open-seo 27,513

PRD generation and conversion skills for the Ralph autonomous agent loop

2 skills

snarktank/ralph 22,224

improve

claude

Point it at a codebase and it figures out what's worth doing — bugs, perf, tech debt, what to build next — then writes plans any agent can execute. It can hand the work to a cheaper model and review the result. It never edits your code.

1 skill

shadcn/improve 11,576

gsd-core

claude

GSD Core is a meta-prompting, context engineering, and spec-driven development system for AI coding agents.

72 skills · 72 commands · 64 agents · hooks

open-gsd/gsd-core 11,494

Maintain rpi?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins2 plugins