discover

Generate research questions from codebase discovery agents and key files.

581|102|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/juicesharp/rpiv-mono --skill discover-juicesharp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: discover
Source: https://github.com/juicesharp/rpiv-mono/tree/main/packages/rpiv-pi/skills/discover
Command: npx skills add https://github.com/juicesharp/rpiv-mono --skill discover-juicesharp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill enables teams to systematically generate trace-quality research questions by coordinating discovery agents, reading key files for depth, and synthesizing findings into dense question paragraphs that serve as inputs to the research workflow. The questions are stored as artifacts in thoughts/shared/questions/.

Core Features & Use Cases

  • Orchestrates discovery agents to surface precise research questions from a codebase.
  • Reads key files to ground questions in actual implementation details and file-level signatures.
  • Produces a compact, portable questions artifact suitable for downstream analysis by the research skill.

Quick Start

Provide a research topic or ticket text, and the skill will generate a questions artifact from discovery.

Frequently Asked Questions about discover

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

FAQPage Schema
How do I generate research questions from a codebase?

You can generate research questions from a codebase by providing a topic input that drives discovery agents to read key files and synthesize findings into dense question paragraphs.

What is codebase discovery for research question generation?

Codebase discovery is the process of orchestrating agents to surface trace-quality research questions by reading key implementation files and grounding questions in actual file-level signatures.

How do I ground research questions in actual codebase implementation details?

Grounding research questions in implementation details involves running discovery agents that perform depth-reading of key files to synthesize trace-quality, dense question paragraphs based on actual signatures.

Can I use a research topic input to drive codebase discovery and question generation?

Yes, you can use a research topic or ticket text as input to drive the discovery agents, which then read key files and synthesize findings into a portable questions artifact.

Where are the generated research questions artifacts stored?

The generated research questions artifacts are stored as compact, portable files in the thoughts/shared/questions/ directory to serve as inputs for downstream analysis.

What is the best way to prepare a codebase for downstream research analysis?

The best way to prepare a codebase for downstream research analysis is to run a discovery skill that generates trace-quality questions, storing the artifacts in thoughts/shared/questions/ for the research pipeline.