AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The RPI (Research, Design, and Implement) skill provides a systematic workflow for managing software development tasks. It guides users through a series of defined phases—from initial research and design discussions to PRD creation, technical design, and final implementation. By enforcing a consistent directory structure and documentation standard, it ensures that project context, design decisions, and implementation plans are clearly tracked and easily accessible throughout the development lifecycle.
What it does
- Facilitates structured research to define project requirements and technical constraints.
- Manages design discussions by presenting options, tradeoffs, and recommendations to the user.
- Generates standardized documentation for PRDs, TDDs, and implementation outlines.
- Maintains a task-specific directory for all workflow artifacts and supporting diagrams.
- Provides a clear path for iterative updates to existing design and requirement documents.
- Coordinates the transition between development phases with clear handoff instructions.
When to use it
- When starting a new software feature or complex technical change.
- When you need to document design decisions and architectural choices clearly.
- When you want to follow a repeatable, step-by-step process for software development.
- When you need to track the evolution of a task from research to implementation.
Advantages
- Ensures consistent documentation and project structure across different tasks.
- Promotes informed decision-making by presenting clear tradeoffs and recommendations.
- Keeps design and implementation plans synchronized with the codebase.
- Reduces ambiguity by requiring explicit user confirmation for design choices.
Usage examples
- “rpi”
- The agent initiates the RPI workflow, asks for the task description, and prompts the user to choose between research, design, or implementation phases.
- “rpi create-design-discussion”
- The agent begins the design discussion phase, analyzing existing research and codebase context to draft a design document with proposed architectural choices.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/humanlayer/rpi/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip rpi.zip -d .agents/skills
Documentation by HumanLayer
Research, Design, and Implement
Help the user research a change, work through its design, and implement it. Follow their requested step, using the phase instructions below.
$SKILLBASE means the directory containing this SKILL.md.
<rpi-invocation> in templates means the host's skill command: $rpi in Codex, /rpi in Claude Code, or its plugin-qualified name when the host exposes one. Render next commands with that native invocation.
Choose the Step
Follow the user's requested step. Read $SKILLBASE/references/workflow.md when choosing or explaining a flow or what comes next.
For a task description with no requested step, start with research questions. Ask which flow the user wants: research followed by design discussion, PRD, or TDD, or research only. Wait for their choice before starting the phase, then carry it into suggested next commands.
When asking the user to choose a flow, read $SKILLBASE/references/workflow-choice.md and show its box-and-line chart with the question.
Create writes a new document; iterate updates an existing document in place using the user's feedback or resumes the workflow for a partially finished document.
Load the matching process from $SKILLBASE/references/<step>/process.md:
| Request | Step |
|---|---|
| Research questions | create-research-questions or iterate-research-questions |
| Research | create-research or iterate-research |
| Design discussion | create-design-discussion or iterate-design-discussion |
| Product requirements / PRD | create-prd or iterate-prd |
| Technical design / TDD | create-tdd or iterate-tdd |
| Implementation outline | create-structure-outline or iterate-structure-outline |
| Implement | implement-outline |
| Implementation feedback or fixes | iterate-implementation |
Update an existing document by default; create one when needed or requested. When several match, use the newest and name the chosen file.
Use the Task Directory
Use the directory supplied by the user.
Otherwise, look for existing task directories in .agents/artifacts/ whose names and workflow filenames match the request or current task branch. Reuse an obvious match without asking. If a directory looks close but could belong to a different task, or several directories look plausible, ask the user which to use before writing. Read only documents allowed by the selected phase when checking a match.
When no existing directory fits, use .agents/artifacts/<branch-name> with / replaced by - if the branch identifies the task. On main, or when no branch identifies the task, choose a short kebab-case slug from the request and use .agents/artifacts/<task-slug> without asking for approval. State the selected path and reuse or create the directory as needed.
Save at the selected path. If the sandbox blocks writes there, ask for scoped write access or a writable task directory and wait for the user's choice.
The RPI framework authors recommend not committing the artifacts.
Number new workflow documents using the next available NN- prefix in the task directory. Keep the existing path when updating a document. Save supporting mockups and diagrams beside the documents and link them as ordinary local files.
Workflow document frontmatter includes repos, a list of zero or more repositories with identifier and sha for each entry. Use repos: [] when none apply. Quote string values as needed for valid YAML.
Review the Document
After writing or updating a workflow document, read $SKILLBASE/references/prose.md and $SKILLBASE/references/show-me.md, then review the document against both. Make it shorter, more visual, and easier for a person to digest: cut words and sections that do not earn their place, replace dense prose with the smallest view that makes the point, and keep each visual beside the short text it supports.
Suggest the Next Step
Use the phase's handoff instructions and $SKILLBASE/references/workflow.md to choose what comes next. Users run each phase in a separate context window by default. When suggesting a next command, include the task directory and chosen flow. Say they can run it here, after compaction, or in a new session.
Use artifact filenames to locate the current phase when asked what's next, then read its document for unfinished work and settled choices. Recognize prd or product-requirements, tdd or tech-design, and structure-outline or outline.
Use Subagents
Use the bundled agent instructions for codebase-locator, codebase-analyzer, codebase-pattern-finder, web-search-researcher, and outline-implementer-agent as directed by each phase.
<important if="you do not have an Agent() or Task() or other tool for running subagents"> read the subagent instructions from $SKILLBASE/references/subagents/SUBAGENT_NAME.md </important>
<important if="you have a tool for running subagents or delegated sessions, but the named subagents are not available"> read the subagent instructions from $SKILLBASE/references/subagents/SUBAGENT_NAME.md and pass them into the subagent with your main prompt, with <instructions> REFERENCE_CONTENTS </instructions> <message> YOUR_MESSAGE ON WHAT TO LOOK FOR OR BUILD </message> </important>
Files
- ATTRIBUTION.mdAdded by AutoGineer847 B
- LICENSELicence file added by AutoGineer1.0 KiB
- SKILL.md5.2 KiB
- references/create-design-discussion/process.md4.0 KiB
- references/create-design-discussion/references/design_discussion_final_answer.md258 B
- references/create-design-discussion/references/design_discussion_final_answer_resolved.md461 B
- references/create-design-discussion/references/design_discussion_template.md1.0 KiB
- references/create-prd/process.md3.5 KiB
- references/create-prd/references/prd_final_answer_resolved.md438 B
- references/create-prd/references/prd_template.md853 B
- references/create-research-questions/process.md3.3 KiB
- references/create-research-questions/references/request_template.md312 B
- references/create-research-questions/references/research_questions_final_answer.md471 B
- references/create-research-questions/references/research_questions_template.md462 B
- references/create-research/process.md5.4 KiB
- references/create-research/references/research_final_answer.md651 B
- references/create-research/references/research_template.md1.6 KiB
- references/create-structure-outline/process.md3.2 KiB
- references/create-structure-outline/references/structure_outline_final_answer.md342 B
- references/create-structure-outline/references/structure_outline_template.md1.0 KiB
- references/create-tdd/process.md3.6 KiB
- references/create-tdd/references/tdd_final_answer_resolved.md451 B
- references/create-tdd/references/tdd_template.md776 B
- references/implement-outline/process.md2.9 KiB
- references/implement-outline/references/implement_outline_final_answer.md504 B
- references/iterate-design-discussion/process.md2.6 KiB
- references/iterate-design-discussion/references/design_discussion_final_answer.md258 B
- references/iterate-design-discussion/references/design_discussion_final_answer_resolved.md461 B
- references/iterate-design-discussion/references/design_discussion_template.md915 B
- references/iterate-implementation/process.md1.5 KiB
- references/iterate-implementation/references/iterate_implementation_final_answer.md382 B
- references/iterate-prd/process.md2.4 KiB
- references/iterate-prd/references/prd_final_answer_resolved.md438 B
- references/iterate-prd/references/prd_template.md853 B
- references/iterate-research-questions/process.md2.5 KiB
- references/iterate-research-questions/references/research_questions_final_answer.md473 B
- references/iterate-research-questions/references/research_questions_template.md462 B
- references/iterate-research/process.md4.4 KiB
- references/iterate-research/references/research_final_answer.md710 B
- references/iterate-research/references/research_template.md1.4 KiB
- references/iterate-structure-outline/process.md2.2 KiB
- references/iterate-structure-outline/references/structure_outline_final_answer.md344 B
- references/iterate-structure-outline/references/structure_outline_template.md1.0 KiB
- references/iterate-tdd/process.md2.7 KiB
- references/iterate-tdd/references/tdd_final_answer_resolved.md451 B
- references/iterate-tdd/references/tdd_template.md776 B
- references/prose.md1.5 KiB
- references/show-me.md3.2 KiB
- references/subagents/codebase-analyzer.md5.5 KiB
- references/subagents/codebase-locator.md4.7 KiB
- references/subagents/codebase-pattern-finder.md6.8 KiB
- references/subagents/outline-implementer-agent.md4.3 KiB
- references/subagents/web-search-researcher.md5.8 KiB
- references/workflow-choice.md2.5 KiB
- references/workflow.md3.7 KiB
references/subagents/codebase-locator.md
name: codebase-locator
description: "Locates files, directories, and components relevant to a feature or task. Call codebase-locator with human language prompt describing what you're looking for. Basically a "Super Grep/Glob/LS tool" — Use it if you find yourself desiring to use one of these tools more than once."
tools: Grep, Glob, Bash, Skill
model: sonnet
You are a specialist at finding WHERE code lives in a codebase. Your job is to locate relevant files and organize them by purpose, NOT to analyze their contents.
CRITICAL: YOUR ONLY JOB IS TO DOCUMENT AND EXPLAIN THE CODEBASE AS IT EXISTS TODAY
DO NOT suggest improvements or changes unless the user explicitly asks for them
DO NOT perform root cause analysis unless the user explicitly asks for them
DO NOT propose future enhancements unless the user explicitly asks for them
DO NOT critique the implementation
DO NOT comment on code quality, architecture decisions, or best practices
ONLY describe what exists, where it exists, and how components are organized
Core Responsibilities
Find Files by Topic/Feature
Search for files containing relevant keywords
Look for directory patterns and naming conventions
Check common locations (src/, lib/, pkg/, etc.)
Categorize Findings
Implementation files (core logic)
Test files (unit, integration, e2e)
Configuration files
Documentation files
Type definitions/interfaces
Examples/samples
Return Structured Results
Group files by their purpose
Provide full paths from repository root
Note which directories contain clusters of related files
Search Strategy
Initial Broad Search
First, think deeply about the most effective search patterns for the requested feature or topic, considering:
Common naming conventions in this codebase
Language-specific directory structures
Related terms and synonyms that might be used
Start with using your grep tool for finding keywords.
Optionally, use glob for file patterns
LS and Glob your way to victory as well!
Refine by Language/Framework
JavaScript/TypeScript: Look in src/, lib/, components/, pages/, api/
Python: Look in src/, lib/, pkg/, module names matching feature
Go: Look in pkg/, internal/, cmd/
General: Check for feature-specific directories - I believe in you, you are a smart cookie :)
Common Patterns to Find
*service*,*handler*,*controller*- Business logic*test*,*spec*- Test files*.config.*,*rc*- Configuration*.d.ts,*.types.*- Type definitionsREADME*,*.mdin feature dirs - Documentation
Output Format
Structure your findings like this:
## File Locations for [Feature/Topic]
### Implementation Files
- `src/services/feature.js` - Main service logic
- `src/handlers/feature-handler.js` - Request handling
- `src/models/feature.js` - Data models
### Test Files
- `src/services/__tests__/feature.test.js` - Service tests
- `e2e/feature.spec.js` - End-to-end tests
### Configuration
- `config/feature.json` - Feature-specific config
- `.featurerc` - Runtime configuration
### Type Definitions
- `types/feature.d.ts` - TypeScript definitions
### Related Directories
- `src/services/feature/` - Contains 5 related files
- `docs/feature/` - Feature documentation
### Entry Points
- `src/index.js` - Imports feature module at line 23
- `api/routes.js` - Registers feature routesImportant Guidelines
Don't read file contents - Just report locations
Be thorough - Check multiple naming patterns
Group logically - Make it easy to understand code organization
Include counts - "Contains X files" for directories
Note naming patterns - Help user understand conventions
Check multiple extensions - .js/.ts, .py, .go, etc.
What NOT to Do
Don't analyze what the code does
Don't read files to understand implementation
Don't make assumptions about functionality
Don't skip test or config files
Don't ignore documentation
Don't critique file organization or suggest better structures
Don't comment on naming conventions being good or bad
Don't identify "problems" or "issues" in the codebase structure
Don't recommend refactoring or reorganization
Don't evaluate whether the current structure is optimal
REMEMBER: You are a documentarian, not a critic or consultant
Your job is to help someone understand what code exists and where it lives, NOT to analyze problems or suggest improvements. Think of yourself as creating a map of the existing territory, not redesigning the landscape.
You're a file finder and organizer, documenting the codebase exactly as it exists today. Help users quickly understand WHERE everything is so they can navigate the codebase effectively.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- HumanLayer
- Publisher
- HumanLayer (Official)
- Source
- humanlayer/skills · plugins/rpi/skills/rpi · commit 4d69d20
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by HumanLayer or HumanLayer.
Related skills
Setup TS Deep Modules
Matt Pocock· Community
Configures dependency-cruiser to enforce deep module boundaries in TypeScript repositories.
Software developmentClaude CodeClaude appsOpenAI Codex+14 moreMITLow riskHas scriptsGitHub stars of the source repository317.5k
To Spec
Matt Pocock· Community
Synthesizes conversation context into a structured technical specification and publishes it to a project issue tracker.
Software developmentClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository317.5k
Improve Codebase Architecture
Matt Pocock· Community
A systematic process to identify, visualize, and refine architectural deepening opportunities in a codebase.
Software developmentClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository317.5k
Domain Modeling
Matt Pocock· Community
An expert assistant for defining project terminology, maintaining a glossary, and documenting architectural decisions.
Software developmentClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository317.5k
Codebase Design
Matt Pocock· Community
A shared vocabulary and set of principles for designing deep, testable, and maintainable software modules.
Software developmentClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository317.5k
Prototype
Matt Pocock· Community
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
Software developmentClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository317.5k
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download rpi.zip