research

Map repository structure and scaffold PDD artifacts into the active plan directory.

Updated Jan 13, 2026
One-click install
npx skills add https://github.com/sammykumar/vibe-flow-agent-orchestrator --skill research-sammykumar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research
Source: https://github.com/sammykumar/vibe-flow-agent-orchestrator/tree/main/.github/skills/research
Command: npx skills add https://github.com/sammykumar/vibe-flow-agent-orchestrator --skill research-sammykumar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Performs repository research, evidence-driven analysis, and scaffolds PDD deliverables (3-RESEARCH.md, 4-SPEC.md, 2-PROGRESS.md) inside the active plan directory to guide complex software projects.

Core Features & Use Cases

  • Evidence gathering: Map codebase structure and surface references from across the repository.
  • Artifact scaffolding: Generate skeletons for 3-RESEARCH.md, 4-SPEC.md, and 2-PROGRESS.md in the active plan.
  • Plan alignment: Integrate findings with plan status and related tasks to support PDD workflows.

Quick Start

Analyze a repository with a request containing keywords like "research" or "spec" to produce the PDD artifacts into .github/plans/... and to surface references via web/fetch_webpage.

Frequently Asked Questions about research

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

FAQPage Schema
How do I analyze a codebase to gather evidence for project planning?

To analyze a codebase for research, you map the repository structure and surface references to gather evidence. This process extracts structural insights and references from across the project to support complex software planning.

What is specification scaffolding and when do I need it for software projects?

Specification scaffolding generates document skeletons like 4-SPEC.md to formalize research findings. You need it when deep investigations require structured artifacts to guide complex software engineering projects.

How do I create PDD artifacts in my active plan directory?

Creating PDD artifacts involves scaffolding files like 3-RESEARCH.md, 4-SPEC.md, and 2-PROGRESS.md directly into the active plan directory. This integrates repository findings with plan status to support specification workflows.

Can I research a repository and fetch external references at the same time?

Repository research can fetch external references simultaneously by mapping the codebase structure and using web fetching tools. This surfaces both internal evidence and external sources to update plan progress.

Does evidence-driven repo research work for any existing codebase?

Evidence-driven repo research works across projects and plans by mapping and analyzing the repository structure. It applies to deep investigations and codebase mapping to generate research findings and specification artifacts.

What are the limitations of using automated research for specification work?

Automated research scaffolds initial PDD artifacts and surfaces references, but the resulting 3-RESEARCH.md and 4-SPEC.md skeletons require manual refinement. It generates structural evidence rather than finalizing complete specifications.