rpi
claudeRPI pipeline: research, plan, implement — a streamlined 3-phase workflow for feature development
3 skills · 3 agents
Deep-work pipeline: 6-phase structured workflow separating research from solutioning
Plugin dw from marketplace context-engineering-workflows in ronsanzone/context-engineering-workflows. Commands read from the repo's manifest — 1 month ago.
dw-01-research-questionsUse when starting a new deep-work task. Decomposes a task description into objective research questions that avoid premature solutioning. Phase 1 of the deep-work pipeline.
dw-02-researchUse when you have research questions from deep-work Phase 1. Objectively investigates the codebase to answer pasted questions without access to the original task description.
dw-03-design-discussionUse when deep-work Phase 2 research is complete. Combines research findings with the original task to explore design options, evaluate tradeoffs, and make decisions interactively.
dw-04-outlineUse when deep-work Phase 3 design decisions are complete. Maps chosen decisions to concrete file changes organized into implementable phases.
dw-05-planUse when deep-work Phase 4 structure outline is complete. Expands the outline into a detailed implementation plan with exact file paths, code patterns, tests, and validation commands.
dw-06-implementUse when deep-work Phase 5 plan is complete. Executes the implementation plan by dispatching a fresh subagent per task with two-stage review (spec compliance → code quality).
codebase-analyzerProduces 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-locatorReturns 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-finderReturns 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
RPI pipeline: research, plan, implement — a streamlined 3-phase workflow for feature development
3 skills · 3 agents
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
15 skills · hooks
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
Backend API design, GraphQL architecture, workflow orchestration with Temporal, and test-driven backend development
9 skills · 1 command · 8 agents
Long-term semantic memory for Claude Code, powered by OpenViking
5 skills · 1 command · 1 MCP server · hooks
AI-supervised issue tracker for coding workflows
1 skill · 1 agent · hooks
MiniMax AI skills library for frontend, fullstack, Android, iOS, shader, GIF sticker, document, presentation, spreadsheet, and multimodal media workflows
18 skills
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.