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.
npx claudepluginhub emingenc/harness-engineering --plugin harness-engineeringThis skill uses the workspace's default tool permissions.
Gather information needed to write a design document. Output goes to
Implements structured self-debugging workflow for AI agent failures: capture errors, diagnose patterns like loops or context overflow, apply contained recoveries, and generate introspection reports.
Monitors deployed URLs for regressions in HTTP status, console errors, performance metrics, content, network, and APIs after deploys, merges, or upgrades.
Provides React and Next.js patterns for component composition, compound components, state management, data fetching, performance optimization, forms, routing, and accessible UIs.
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: