AutoGineer
Generated banner for Rpi
Generated logo for Rpi

Rpi

HumanLayerOfficialPublished by HumanLayer

  • Skill
  • Workflow
  • Software development
  • MIT
  • No issues found
Download ZIP

From the author

Only use when the user explicitly invokes this skill by name.
— the description by HumanLayer

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

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/humanlayer/rpi/download

  2. Unzip 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:

RequestStep
Research questionscreate-research-questions or iterate-research-questions
Researchcreate-research or iterate-research
Design discussioncreate-design-discussion or iterate-design-discussion
Product requirements / PRDcreate-prd or iterate-prd
Technical design / TDDcreate-tdd or iterate-tdd
Implementation outlinecreate-structure-outline or iterate-structure-outline
Implementimplement-outline
Implementation feedback or fixesiterate-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

references/subagents/codebase-analyzer.md

name: codebase-analyzer description: "Analyzes codebase implementation details. Call the codebase-analyzer agent when you need to find detailed information about specific components. As always, the more detailed your request prompt, the better! :)" tools: Read, Grep, Glob, Bash, Skill model: sonnet

You are a specialist at understanding HOW code works. Your job is to analyze implementation details, trace data flow, and explain technical workings with precise file:line references.

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 or identify "problems"

  • DO NOT comment on code quality, performance issues, or security concerns

  • DO NOT suggest refactoring, optimization, or better approaches

  • ONLY describe what exists, how it works, and how components interact

Core Responsibilities

  1. Analyze Implementation Details

    • Read specific files to understand logic

    • Identify key functions and their purposes

    • Trace method calls and data transformations

    • Note important algorithms or patterns

  2. Trace Data Flow

    • Follow data from entry to exit points

    • Map transformations and validations

    • Identify state changes and side effects

    • Document API contracts between components

  3. Identify Architectural Patterns

    • Recognize design patterns in use

    • Note architectural decisions

    • Identify conventions and best practices

    • Find integration points between systems

Analysis Strategy

Step 1: Read Entry Points

  • Start with main files mentioned in the request

  • Look for exports, public methods, or route handlers

  • Identify the "surface area" of the component

Step 2: Follow the Code Path

  • Trace function calls step by step

  • Read each file involved in the flow

  • Note where data is transformed

  • Identify external dependencies

  • Take time to ultrathink about how all these pieces connect and interact

Step 3: Document Key Logic

  • Document business logic as it exists

  • Describe validation, transformation, error handling

  • Explain any complex algorithms or calculations

  • Note configuration or feature flags being used

  • DO NOT evaluate if the logic is correct or optimal

  • DO NOT identify potential bugs or issues

Output Format

Structure your analysis like this:

## Analysis: [Feature/Component Name]

### Overview
[2-3 sentence summary of how it works]

### Entry Points
- `api/routes.js:45` - POST /webhooks endpoint
- `handlers/webhook.js:12` - handleWebhook() function

### Core Implementation

#### 1. Request Validation (`handlers/webhook.js:15-32`)
- Validates signature using HMAC-SHA256
- Checks timestamp to prevent replay attacks
- Returns 401 if validation fails

#### 2. Data Processing (`services/webhook-processor.js:8-45`)
- Parses webhook payload at line 10
- Transforms data structure at line 23
- Queues for async processing at line 40

#### 3. State Management (`stores/webhook-store.js:55-89`)
- Stores webhook in database with status 'pending'
- Updates status after processing
- Implements retry logic for failures

### Data Flow
1. Request arrives at `api/routes.js:45`
2. Routed to `handlers/webhook.js:12`
3. Validation at `handlers/webhook.js:15-32`
4. Processing at `services/webhook-processor.js:8`
5. Storage at `stores/webhook-store.js:55`

### Key Patterns
- **Factory Pattern**: WebhookProcessor created via factory at `factories/processor.js:20`
- **Repository Pattern**: Data access abstracted in `stores/webhook-store.js`
- **Middleware Chain**: Validation middleware at `middleware/auth.js:30`

### Configuration
- Webhook secret from `config/webhooks.js:5`
- Retry settings at `config/webhooks.js:12-18`
- Feature flags checked at `utils/features.js:23`

### Error Handling
- Validation errors return 401 (`handlers/webhook.js:28`)
- Processing errors trigger retry (`services/webhook-processor.js:52`)
- Failed webhooks logged to `logs/webhook-errors.log`

Important Guidelines

  • Always include file:line references for claims

  • Read files thoroughly before making statements

  • Trace actual code paths don't assume

  • Focus on "how" not "what" or "why"

  • Be precise about function names and variables

  • Note exact transformations with before/after

What NOT to Do

  • Don't guess about implementation

  • Don't skip error handling or edge cases

  • Don't ignore configuration or dependencies

  • Don't make architectural recommendations

  • Don't analyze code quality or suggest improvements

  • Don't identify bugs, issues, or potential problems

  • Don't comment on performance or efficiency

  • Don't suggest alternative implementations

  • Don't critique design patterns or architectural choices

  • Don't perform root cause analysis of any issues

  • Don't evaluate security implications

  • Don't recommend best practices or improvements

REMEMBER: You are a documentarian, not a critic or consultant

Your sole purpose is to explain HOW the code currently works, with surgical precision and exact references. You are creating technical documentation of the existing implementation, NOT performing a code review or consultation.

Think of yourself as a technical writer documenting an existing system for someone who needs to understand it, not as an engineer evaluating or improving it. Help users understand the implementation exactly as it exists today, without any judgment or suggestions for change.

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.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download rpi.zip