From harness-engineering
Conduct codebase research using parallel sub-agents and PTC scripts. Use when user says "research", "investigate", "explore", "understand how", "find out about", "analyze the codebase", or before planning a feature. This is the first phase of Track 2.
How this skill is triggered — by the user, by Claude, or both
Slash command
/harness-engineering:researcherThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Gather information needed to write a design document. Output goes to
Gather information needed to write a design document. Output goes to
workspace/research/<topic>.md for the planner to consume.
Before searching, identify 3-5 specific questions that need answering:
Run local codebase search first:
python3 ${CLAUDE_PLUGIN_ROOT}/skills/researcher/scripts/search_local.py <term1> <term2> [--pattern "*.py"]
This returns a JSON summary of matches. Read only the most relevant files identified.
If local search is insufficient, spawn Explore sub-agents for deeper investigation. Each agent gets a fresh context window — no context bleed.
Spawn agents for INDEPENDENT questions in parallel (single message, multiple Agent calls):
Agent(subagent_type="Explore", prompt="Research question 1: ...")
Agent(subagent_type="Explore", prompt="Research question 2: ...")
Each agent should:
For library/framework documentation, use context7 MCP:
Aggregate findings into a research summary:
python3 ${CLAUDE_PLUGIN_ROOT}/skills/researcher/scripts/format_findings.py \
--topic "<topic>" --output "workspace/research/<topic>.md"
The script reads findings from stdin (JSON) and writes formatted markdown.
Write the research file and show the user:
/plan" or "Need more research on X"Input: "/research authentication flow" Process:
Input: "/research api error handling patterns" Process:
npx claudepluginhub emingenc/harness-engineering --plugin harness-engineeringDocuments codebases as-is by spawning parallel sub-agents to research files and synthesize findings into reports. Activates on /research or codebase understanding requests.
Spawns parallel sub-agents to research codebase areas and synthesizes findings into a document. Great for deep understanding of codebase or answering technical questions.
Explores codebase topics by searching prior knowledge and conducting multi-angle analysis, outputting structured findings. Supports /research command and optional auto mode.