agent-researcher

Explore codebases and documentation to produce source-cited research findings.

8|13|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/queen-of-code/AI-DLC --skill agent-researcher
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-researcher
Source: https://github.com/queen-of-code/AI-DLC/tree/main/plugins/ai-dlc-skills/skills/agents/agent-researcher
Command: npx skills add https://github.com/queen-of-code/AI-DLC --skill agent-researcher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of fragmented, time-consuming manual research across codebases, documentation, and curated brain-mcp collections by producing concise, source-cited findings that support planning and decision making.

Core Features & Use Cases

  • Structured Research Briefs: Produces a planning-mode research brief that answers whether similar features exist, identifies technical and user context, and surfaces related ADRs or specs.
  • Targeted Investigations: Clarifies ambiguous questions, reads broadly (README, ADRs, index files) then drills into specifics, and returns findings with file/URL citations and confidence levels.
  • Read-only Evidence Gathering: Operates without modifying code or files, suitable for planning, design research, build-time investigations, and review audits across project repositories and brain collections.

Quick Start

Ask the researcher to produce a research brief for the feature "single sign-on integration" using the project's brain collection and codebase.

Frequently Asked Questions about agent-researcher

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

FAQPage Schema
How do I research a codebase to find related ADRs and implementation context for planning?

Codebase research for planning involves reading broadly across documentation, ADRs, and index files, then drilling into specifics. This Skill performs read-only exploration of repositories and brain-mcp collections to answer whether similar features exist and surfaces related specs with file path citations.

What is the best way to generate a structured research brief from project documentation?

The best way to generate a structured research brief is to query a read-only tool that reads project documentation and returns concise findings with URL citations. This Skill produces planning-mode briefs that answer feature questions and surface related ADRs with confidence estimates.

Can I investigate external sources and brain-mcp collections without modifying my code?

Yes, investigating external sources and brain-mcp collections without modifying code is possible using read-only access. This Skill gathers evidence without writing to files, making it suitable for design research, build-time investigations, and review audits across project repositories.

Does codebase research require configuring turn and timeout limits?

Yes, codebase research requires adhering to configured turn and timeout limits to manage exploration scope. This Skill respects configured limits while returning confidence estimates and file path citations for every finding it surfaces from the repository.

How do I get source-cited findings with confidence levels for a feature investigation?

Getting source-cited findings with confidence levels requires a research tool that reads your project's brain collection and codebase. This Skill returns structured findings with file paths, URLs, and confidence estimates for every answer it surfaces.

When do I need a read-only research tool for software engineering planning?

You need a read-only research tool for software engineering planning when you want to answer whether similar features exist without risking code modifications. This Skill is suitable for planning, design research, build-time investigations, and review audits across project repositories.