parallel-analysis

Parallel Analysis (Multi-Agent Fan-Out)

Split a large analysis into independent read-only lanes, run them concurrently with the resolved ready adapters, merge the lane reports, and verify merged claims with a skeptical refutation pass. One round of parallel lanes replaces slow serial reading; the verification lane replaces manual double-checking.

This skill is project-agnostic: it works in any repo where the kit is installed, using that repo's backbone.yml (if present) for boundaries.

Best Use

• Repo-wide questions ("where is X handled, what depends on Y").
• Reviewing a large uncommitted diff by concern (backend vs frontend vs i18n vs scripts).
• Reading several large docs, plans, or reference trees at once.
• Pre-change impact analysis across packages/apps listed in backbone.yml paths.apps.
• Consistency audits (docs vs code, rules vs skills, config vs actual layout).

Do NOT use for single-file questions or quick lookups; direct reads are faster.

Orchestration preference and executor setup

Immediately before the first lane dispatch, follow .vibekit/docs/ORCHESTRATION_MODES.md in the parent session. Resolve Default, Auto, or Custom before selecting executors. The preference is global project state; .vibekit/parallel-analysis.json stores only skill-specific adapter details.

1. Read a remembered orchestration preference when present. If it is not remembered, use the parent runtime's native structured-question tool or its plain parent-conversation fallback.
2. Inspect .vibekit/parallel-analysis.json when present. Reuse only adapters whose non-mutating preflight still passes. A stale executor cache never suppresses an unresolved global mode question.
3. Build a bounded inventory of the active provider plus Codex, Claude, Cursor, Grok, and Kimi adapters that are already installed or exposed.
4. Classify every candidate as ready, installed-unverified, or unavailable using the shared contract. Auto uses ready adapters only.
5. Apply the selected mode:
   • Default: use the active provider's native child-agent facility and default model. If the host exposes no such facility, run the lanes sequentially in the current parent; do not switch providers.
   • Auto: split the independent lanes first, then route each lane to the lowest-cost ready model that satisfies context, tool, risk, and verification requirements. A heterogeneous set is allowed.
   • Custom: validate the user's role or lane assignments against the ready inventory. Ask in batches of at most three native questions when an assignment is missing.