rpi-research

Investigate codebases read-only and produce a structured findings report.

Updated Oct 19, 2025
One-click install
npx skills add https://github.com/igor1309/skills --skill rpi-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rpi-research
Source: https://github.com/igor1309/skills/tree/main/rpi-research
Command: npx skills add https://github.com/igor1309/skills --skill rpi-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide a disciplined, read-only research phase that investigates a codebase and reports factual findings, risks, and unknowns without proposing solutions or making code changes. This prevents premature planning or implementation decisions and preserves a clear separation between discovery and action.

Core Features & Use Cases

  • Structured Research Output: Produces a report with Task Understanding, Findings, Risks & Unknowns, Questions, and Large-Scope Mode guidance when applicable.
  • Read-only Codebase Investigation: Scans referenced documents and repository files to surface relevant files, patterns, constraints, and representative examples without modifying any files.
  • Workflow Guardrails: Explicitly avoids suggestions, implementation details, and automatic transitions to planning or coding phases, and asks before switching modes.
  • Use Case: Use when you need an evidence-based understanding of architecture, dependencies, and potential risks before writing a specification or implementation plan.

Quick Start

Invoke /rpi-research to run a read-only codebase investigation and receive a structured findings report without solution proposals.

Frequently Asked Questions about rpi-research

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I investigate a codebase to identify risks and dependencies before planning implementation?

Investigating a codebase for risk assessment requires a read-only research phase that scans repository files to surface architecture, dependencies, and constraints. A structured findings report delivers factual understanding of unknowns to prevent premature implementation decisions.

What is the best way to document codebase findings without proposing solutions or making code changes?

Documenting codebase findings without proposing solutions requires a disciplined read-only research phase. It outputs structured sections for Task Understanding, Findings, Risks, and Questions, maintaining clear separation between discovery and action.

How do I start a read-only codebase investigation to understand architecture and constraints?

Start a read-only codebase investigation by invoking the research workflow on referenced documents and repositories. It scans files to surface relevant patterns and representative examples, outputting a structured findings report for the early research phase.

Does codebase research prevent automatic transitions to planning or implementation phases?

Codebase research includes workflow guardrails that explicitly avoid suggestions and implementation details. It prevents automatic transitions to planning or coding phases and asks before switching modes, ensuring discovery remains separate from action.

When should I use a structured codebase research phase instead of direct implementation?

Use a structured codebase research phase when you need evidence-based understanding of architecture, dependencies, and potential risks before writing a specification or implementation plan. It is required for early workflows where discovering unknowns prevents premature decisions.