pre-dev-research

Dispatch parallel research agents to produce consolidated research.md with references.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/withmartian-sandbox/ghrc-x-3126672651424eddb640ecc81321a665 --skill pre-dev-research-withmartian-sandbox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pre-dev-research
Source: https://github.com/withmartian-sandbox/ghrc-x-3126672651424eddb640ecc81321a665/tree/main/pm-team/skills/pre-dev-research
Command: npx skills add https://github.com/withmartian-sandbox/ghrc-x-3126672651424eddb640ecc81321a665 --skill pre-dev-research-withmartian-sandbox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents planning and implementation mistakes by gathering targeted research before writing PRDs or TRDs, ensuring decisions are grounded in codebase reality, external best practices, and framework constraints.

Core Features & Use Cases

  • Parallel research agents: Dispatches repo-research-analyst, best-practices-researcher, and framework-docs-researcher in parallel to collect file:line references, external URLs, and version constraints.
  • Consolidated output: Produces docs/pre-dev/{feature-name}/research.md with metadata, an executive summary, code references, URLs, documented tech versions, and a synthesis section to inform PRD/TRD authors.
  • Gate 0 validation: Enforces a blocking checklist requiring research mode, all three agent outputs, at least one file:line reference (when applicable), external URLs (when applicable), and tech stack documentation before proceeding.
  • Use cases: Greenfield feature planning, modifying existing functionality, and integrating external systems where discovery of patterns and constraints is required.

Quick Start

Run the pre-dev-research skill for the new payments feature to generate docs/pre-dev/payments/research.md with agent outputs and validation.

Frequently Asked Questions about pre-dev-research

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

FAQPage Schema
How do I gather codebase research and best practices before writing a PRD?

Pre-development research dispatches parallel agents to collect codebase references, external best practices, and framework documentation into a consolidated research.md file to inform your PRD or TRD.

When do I need pre-development research for feature planning?

Pre-development research is needed when planning greenfield features, modifying existing functionality, or integrating external systems to discover codebase patterns and framework constraints before implementation.

What is a Gate 0 validation checklist for feature research?

Gate 0 validation is a blocking checklist requiring research mode, all three research agent outputs, file:line references, external URLs, and documented tech stack versions before proceeding to write a PRD.

Can I analyze my codebase and external framework docs at the same time for a TRD?

Yes, parallel research agents dispatch simultaneously to collect repo file:line references, external best practice URLs, and framework version constraints, consolidating all outputs into a single research.md file.

What's the best way to document tech stack versions and constraints before modifying an existing feature?

Running pre-dev research dispatches a framework-docs-researcher agent alongside codebase and best practices agents to document specific tech versions and constraints in a consolidated research.md file.

What happens if one of the research agents fails to return output during pre-development research?

The Gate 0 blocking validation checklist requires all three research agents' outputs, so if any agent fails to return references, URLs, or framework documentation, the research process blocks completion.