deepresearch

Plugin deepresearch from marketplace ccplugin-market in lazygophers/ccplugin. Commands read from the repo's manifest — 2 days ago.

Skills (6)

• deep-research

  This skill should be used when the user asks to "research X", "deep dive into X", "compare A vs B", "evaluate this project", or requests evidence-backed technical research, architecture review, or technology selection.

• evidence-synthesizer

  This skill should be used when the user needs to synthesize research evidence into conclusions and recommendations. Typical triggers include summarizing evidence, reconciling conflicting sources, or deriving recommendations.

• report-writer

  This skill should be used when the user needs a structured research report or formatted output. Typical triggers include writing executive summaries, technical reports, comparison tables, or checklists.

• research-planner

  This skill should be used when the user needs to plan a research investigation or clarify research scope and questions. Typical triggers include creating a research plan, defining research questions, or structuring a study. Use when planning or scoping research tasks.

• source-retriever

  This skill should be used when the user needs to retrieve sources for research or build a source list. Typical triggers include collecting sources, searching for documentation, or assembling references.

• source-validator

  This skill should be used when the user needs to validate sources, verify claims, or rate evidence quality. Typical triggers include verifying citations, checking credibility, or rating sources.

Subagents (4)

• architecture-advisor

  Use this agent when the user asks for architecture review, system design feedback, or refactoring strategy. Typical triggers include architecture assessment, design review, and migration or evolution planning. See "When to invoke" in the agent body for worked scenarios.

• code-analyst

  Use this agent when the user asks for code quality review, technical debt analysis, or performance bottleneck investigation. Typical triggers include "code quality", "tech debt", or "performance issue" requests and audits of a codebase or module. See "When to invoke" in the agent body for worked sce

• project-assessor

  Use this agent when the user asks to evaluate a project, assess dependency risks, or audit supply-chain security. Typical triggers include GitHub project assessment, dependency audit, or license and maintenance risk checks. See "When to invoke" in the agent body for worked scenarios.

• research-strategist

  Use this agent when the user asks for technology selection, framework comparisons, or research planning. Typical triggers include comparing A vs B, evaluating options for a stack, and requesting a structured research approach. See "When to invoke" in the agent body for worked scenarios.

Similar plugins