parallel-exploration

Decompose codebase questions into independent parallel tracks and synthesize cited findings.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/mpsuesser/workspace --skill parallel-exploration-mpsuesser
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: parallel-exploration
Source: https://github.com/mpsuesser/workspace/tree/main/dotconfig/opencode/skills/parallel-exploration
Command: npx skills add https://github.com/mpsuesser/workspace --skill parallel-exploration-mpsuesser

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you explore complex codebase questions by splitting the work into independent investigation tracks and then combining their results into a coherent answer.

Core Features & Use Cases

  • Parallel track decomposition: Breaks a question into 3–6 orthogonal dimensions, runs each as an independent track, and verifies independence.
  • Gated evidence gathering: Uses checkpoints to ensure the context is understood, findings are evidence-backed, and the final summary is complete.
  • Orthogonal module specialist overlay: Detects complex modules and reviews their efficiency and idiomatic usage strictly within module usage, returning file:line citations.

Use cases include understanding architecture, investigating multi-cause bugs, and researching cross-cutting patterns where multiple perspectives reduce blind spots.

Quick Start

Use the parallel-exploration skill to decompose your codebase question into independent tracks, run evidence-gated exploration for each track (including module specialist review for complex modules), and return a unified synthesis with cited findings.

Frequently Asked Questions about parallel-exploration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I investigate multi-cause bugs across a complex codebase?

Multi-cause bug investigation benefits from decomposing a question into 3–6 orthogonal parallel tracks, running evidence-gated exploration for each, and aggregating findings into a unified synthesis with file:line citations to reduce blind spots.

What is the best way to understand software architecture through codebase exploration?

Codebase exploration for architecture understanding is improved by splitting the question into independent dimensions, verifying track orthogonality, and combining the parallel results into a coherent, evidence-backed summary.

How do I research cross-cutting patterns without overlapping exploration efforts?

Researching cross-cutting patterns without overlap requires orthogonal track independence verification, ensuring each parallel perspective covers distinct dimensions before aggregating the findings into a unified synthesis.

Can I review complex modules using only their local usage context?

Reviewing complex modules using only local usage context is supported by a specialist overlay that detects these modules and evaluates their efficiency and idiomatic usage, returning findings with file:line citations.

When should I use parallel reasoning instead of sequential codebase search?

Parallel reasoning is preferred over sequential codebase search when investigating multi-cause bugs or cross-cutting patterns where multiple perspectives improve coverage, whereas simple linear queries suit isolated module reviews.