ring:pre-dev-research

Orchestrates parallel pre-dev research across codebase patterns, best practices, and framework docs.

4|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/LerianStudio/ring-for-opencode --skill ring-pre-dev-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ring:pre-dev-research
Source: https://github.com/LerianStudio/ring-for-opencode/tree/main/assets/skill/pre-dev-research
Command: npx skills add https://github.com/LerianStudio/ring-for-opencode --skill ring-pre-dev-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill orchestrates a three-agent pre-dev research workflow to gather codebase patterns, external best practices, and framework documentation before PRD/TRD, ensuring planning is grounded in current realities.

Core Features & Use Cases

  • Parallel research dispatch: triggers codebase patterns research, external practices, and framework docs in parallel.
  • Mode-aware planning: supports greenfield, modification, and integration research modes with clear agent focus.
  • Structured output: generates docs/pre-dev/{feature-name}/research.md with file:line references and external URLs.

Quick Start

Run the pre-dev research workflow to generate a feature-specific research document at docs/pre-dev/{feature-name}/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 automate pre-dev research for codebase patterns and framework docs before writing a PRD?

Pre-dev research automation dispatches parallel agents to gather codebase patterns, external best practices, and framework documentation, generating a structured research.md file with file:line references and external URLs before PRD creation.

What is the best way to gather existing codebase patterns and best practices for greenfield development planning?

The best approach for greenfield planning uses mode-aware parallel research agents to collect framework docs and external best practices simultaneously, ensuring new feature planning is grounded in current technical realities.

How does parallel agent dispatch work for pre-development research workflows?

Parallel agent dispatch triggers three specialized researchers simultaneously—codebase patterns, external practices, and framework docs—reducing research time and producing unified structured output with precise file:line references.

Can I run pre-dev research for both modification and integration scenarios, or only greenfield projects?

Yes, pre-dev research supports mode-aware planning across greenfield, modification, and integration scenarios, dispatching focused agents to analyze existing code patterns and framework docs relevant to each specific context.

Where should pre-development research outputs be stored for downstream PRD and TRD consumption?

Pre-development research outputs should be stored as structured markdown at docs/pre-dev/{feature-name}/research.md, containing file:line references and external URLs for direct integration into subsequent PRD and TRD planning phases.