research

Map affected codebase domains and document evidence for specifications.

8|Updated Jun 18, 2026

Search Tags:#refactoring #architecture analysis #codebase research #dependency mapping #test discovery #context report

Ready to run

npx skills add https://github.com/ddobrin/plan-skills --skill research-ddobrin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: research
Source: https://github.com/ddobrin/plan-skills/tree/main/plugins/orchestrator/skills/research
Command: npx skills add https://github.com/ddobrin/plan-skills --skill research-ddobrin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents premature specifications and plans by grounding feature, bug, and refactor work in evidence from the existing codebase.

Core Features & Use Cases

Codebase Investigation: Identify affected modules, architectural patterns, dependencies, integration points, and constraints.
Test and Risk Discovery: Locate existing tests, expose coverage gaps, and document likely failure modes.
Context Report Creation: Produce a structured report with file-based evidence for downstream discovery and product-planning phases.

Quick Start

Use the research skill to investigate the requested change and write an evidence-based context report in the plans/research directory.

Frequently Asked Questions about research

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

FAQPage Schema

How do I map codebase dependencies before refactoring?▼

Codebase dependency mapping before refactoring identifies affected modules, architectural patterns, integration points, and constraints. It produces an evidence-based context report in the plans/research directory to ground downstream specification and implementation planning.

What is the best way to discover existing test coverage for a bug fix?▼

Test discovery for a bug fix locates existing tests, exposes coverage gaps, and documents likely failure modes. It investigates the requested change area to produce a structured context report with file-based evidence for product planning.

Do I need a context report before writing an implementation plan?▼

A context report is needed before writing an implementation plan to prevent premature specifications. It grounds feature, bug, and refactor work in evidence from the existing codebase, mapping affected domains and documenting constraints before planning begins.

Can I analyze architecture patterns without modifying source files?▼

Architecture analysis can be performed without modifying source files. The investigation uses built-in file viewing, directory listing, search, and subagent tools while preserving all source files as read-only during the codebase research process.

When should I do codebase research for a new feature?▼

Codebase research for a new feature should be done when no existing context report covers the request. It maps the affected codebase domain and documents evidence needed before writing a specification or implementation plan.