parallel-investigate
Skill2 starsChanged 4 months agoNo licenceView on GitHub
Fans out multiple agents in parallel via the Workflow tool to investigate a codebase question — bug root cause tracing, cross-file or cross-repository behavior tracing, "why does X happen for some cases but not others" questions — then synthesizes a ranked, file:line-cited answer in chat. The point of this skill is explicitness: it announces the investigation dimensions and agent count before launching, narrates progress, and reports a structured synthesis, rather than leaving multi-agent orchestration as an implicit background behavior the user can't see into. Supports investigations that span more than one local repository on disk (e.g. a backend service and a client app that talks to it). Investigation only — does not edit code or fix anything; pair with another skill or a follow-up request for that. Use when the user wants to investigate a bug, trace behavior across files or repositories, understand why something happens under some conditions but not others, or explicitly asks for a parallel/multi-agent investigation. Trigger phrases: "parallel-investigate", "/parallel-investigate", "並列で調査して", "並列調査", "複数エージェントで調べて", "複数エージェントで並列調査して", "investigate this in parallel", "fan out and investigate", "investigate across repos", "trace this across repositories".
In this repository58 other files it gives its agents.
- AGENTS.mdAGENTS.md
- adversarial-panelSkill
- agents-initSkill
- agent-swarmSkill
- chrome-useSkill
- codex-cliSkill
- codex-serverSkill
- confluenceSkill
- deepenSkill
- dev-workflowSkill
- diagnoseSkill
- dotnet-seniorSkill
- e2e-testSkill
- en-to-ja-explainerSkill
- figma-shot-boardSkill
- gdrive-cliSkill
- grill-meSkill
- grill-to-implSkill
- grill-with-docsSkill
- handoffSkill
- improve-codebase-architectureSkill
- japanese-tech-writingSkill
- jira-cliSkill
- local-skill-factorySkill
- logo-imageSkill
- my-gdriveSkill
- my-skill-factorySkill
- naturalize-jaSkill
- natural-japaneseSkill
- notion-cliSkill
- openai-cliSkill
- orch-qaSkill
- playwright-cliSkill
- pm-reviewSkill
- postmortemSkill
- prd-councilSkill
- prototypeSkill
- pr-reviewSkill
- recap-to-notionSkill
- review-localSkill
- scenario-genSkill
- self-pr-reviewSkill
- session-handoverSkill
- session-recapSkill
- session-watchSkill
- skill-improveSkill
- slack-cliSkill
- slack-to-ticketSkill
- subagent-genSkill
- tddSkill
- test-scenarioSkill
- to-prdSkill
- triageSkill
- ui-spec-simSkill
- well-arch-costSkill
- well-arch-reliabilitySkill
- well-arch-securitySkill
- zoom-outSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 8 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

