ring:pre-dev-research

Coordinate four parallel research agents to generate a Gate 0 research.md document.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/LucasMalessa/TheRing --skill ring-pre-dev-research-lucasmalessa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ring:pre-dev-research
Source: https://github.com/LucasMalessa/TheRing/tree/main/pm-team/skills/pre-dev-research
Command: npx skills add https://github.com/LucasMalessa/TheRing --skill ring-pre-dev-research-lucasmalessa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gate 0 research often stalls feature planning by missing verification of codebase patterns, external best practices, and user needs. This skill orchestrates a formal, parallel research workflow that grounds pre-dev decisions in documented evidence.

Core Features & Use Cases

  • Dispatches four research agents in parallel to collect codebase patterns, external best practices, framework documentation, and user research findings.
  • Generates a consolidated research.md with file:line references, topology-aware outputs for single-repo, monorepo, or multi-repo setups, and a synthesis section for PRD guidance.
  • Ensures documentation of tech stack versions and search of docs/solutions for prior implementations to prevent rework.

Quick Start

Trigger Gate 0 research by running the pre-dev full or feature command, which will dispatch four agents and produce research.md.

Frequently Asked Questions about ring:pre-dev-research

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

FAQPage Schema
How do I conduct pre-development research before creating a PRD or TRD?

Pre-development research can be conducted by dispatching parallel research agents to gather codebase patterns, external best practices, framework docs, and user research findings into a comprehensive Gate 0 research document. This aggregates findings into research.md with file:line references and a synthesis section to guide PRD creation.

What is Gate 0 research and how does it prevent rework in feature planning?

Gate 0 research is a formal pre-development workflow that grounds feature decisions in documented evidence. It verifies codebase patterns, external best practices, and user needs by searching docs/solutions for prior implementations and documenting tech stack versions from manifests, preventing duplicated effort and planning stalls.

How do I document codebase patterns and external best practices with file references?

You can document codebase patterns and best practices by running parallel research agents that aggregate findings into a consolidated research.md file. The output includes specific file:line references, topology-aware outputs for single-repo or multi-repo contexts, and a synthesis section for product guidance.

Can I run pre-dev research in a multi-repo or monorepo setup?

Yes, pre-dev research supports topology-aware outputs for single-repo, monorepo, and multi-repo setups. The research agents adapt to your repository structure to collect framework documentation and codebase patterns across your specific project topology.

Does pre-dev research include user research and UX findings for feature planning?

Yes, the parallel research workflow includes dedicated product and UX research components. One of the four dispatched agents specifically collects user research findings to ensure pre-development decisions account for user needs alongside technical framework documentation and codebase patterns.

What's the best way to gather framework docs and tech stack versions before coding?

The best way is to dispatch parallel research agents that automatically document tech stack versions from manifests and collect framework documentation. This aggregates external best practices and prior solutions from docs/solutions into a single research.md file before development begins.