parallel-investigation
Coordinates parallel investigation threads to simultaneously explore multiple hypotheses or root causes across different system areas. Use when debugging production incidents, slow API performance, multi-system integration failures, or complex bugs where the root cause is unclear and multiple plausible theories exist; when serial troubleshooting is too slow; or when multiple investigators can divide root-cause analysis work. Provides structured phases for problem decomposition, thread assignment, sync points with Continue/Pivot/Converge decisions, and final report synthesis.
Profile →npx skills add rohitg00/skillkit --skill parallel-investigation --agent codex
Same command for any agent — swap --agent for claude-code, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Parallel Investigation Coordinate parallel investigation threads to explore multiple hypotheses simultaneously. Most effective for production incidents, performance regressions, or integration failures where the root cause is unclear. ## Core Principle **When uncertain, explore multiple paths in parallel. Converge when evidence points to an answer.** Parallel investigation reduces time-to-solution by eliminating serial bottlenecks. ## Investigation Structure ### Phase 1: Problem Decomposition Break the problem into independent investigation threads: ``` Problem: API responses are slow Investigation Threads: ├── Thread A: Database performance │ └── Check slow queries, indexes, connection pool ├── Thread B: Application code │ └── Profile endpoint handlers, check for N+1 ├── Thread C: Infrastructure │ └── Check CPU, memory, network latency └── Thread D: External services └── Check third-party API response times ``` Each thread should be independent (no blocking dependencies), focused (clear scope), and time-boxed. ### Phase 2: Thread Assignment Assign threads with clear ownership: ```markdown ## Thread A: Database Performance **Investigator:** [Name/Agent A] **Duration:** 30 minutes
- Core Principle
- Investigation Structure
- Phase 1: Problem Decomposition
- Phase 2: Thread Assignment
- Phase 3: Parallel Execution
- Phase 4: Sync Points
- Phase 5: Convergence
- Coordination Patterns
- Communication Protocol
- During Investigation
- At Sync Point
- Decision Framework
- Time Management
- Documentation
What does the parallel-investigation skill do?
Coordinates parallel investigation threads to simultaneously explore multiple hypotheses or root causes across different system areas. Use when debugging production incidents, slow API performance, multi-system integration failures, or complex bugs where the root cause is unclear and multiple plausible theories exist; when serial troubleshooting is too slow; or when multiple investigators can divide root-cause analysis work. Provides structured phases for problem decomposition, thread assignment, sync points with Continue/Pivot/Converge decisions, and final report synthesis.
How do I install it?
Run `npx skills add rohitg00/skillkit --skill parallel-investigation --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From rohitg00/skillkit, a repository with 1,422 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.