parallel-execution

Coordinate parallel or serial execution lanes against a shared requirement contract.

3|Updated Dec 7, 2025
One-click install
npx skills add https://github.com/Grimblaz/agent-orchestra --skill parallel-execution-grimblaz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: parallel-execution
Source: https://github.com/Grimblaz/agent-orchestra/tree/main/skills/parallel-execution
Command: npx skills add https://github.com/Grimblaz/agent-orchestra --skill parallel-execution-grimblaz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Coordinates and governs multiple execution paths (parallel or serial) against a single shared contract to ensure predictable outcomes and easier triage.

Core Features & Use Cases

  • Declare one Execution Mode before delegation: parallel or serial.
  • Define and enforce a shared Requirement Contract prior to running lanes.
  • Manage convergence gates and post-run triage to classify and route failures.

Quick Start

Initiate a session to compare parallel and serial lanes under a single shared contract.

Frequently Asked Questions about parallel-execution

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

FAQPage Schema
How do I orchestrate parallel execution safely across multiple implementation paths?

Parallel execution orchestration requires declaring a single Execution Mode and defining a shared Requirement Contract before delegating lanes, ensuring predictable outcomes through enforced convergence gates and post-run conformance checks.

What is a convergence gate in workflow orchestration?

A convergence gate in workflow orchestration is a post-run checkpoint that classifies and routes failures, ensuring multiple execution paths conform to the shared Requirement Contract before merging results.

When do I need parallel versus serial execution lanes for multi-path implementation?

You need parallel execution lanes for concurrent multi-path implementation when speed is critical, while serial lanes handle sequential dependencies; both require a shared contract to coordinate triage routing safely.

How do I set up a shared requirement contract for triage routing across Code-Smith and Test-Writer?

Setting up a shared requirement contract involves defining a single execution contract prior to running lanes, which governs triage routing across Code-Smith and Test-Writer and enforces post-run conformance checks.

Does parallel execution orchestration work without predefined convergence gates?

Parallel execution orchestration without convergence gates bypasses post-run triage routing, risking unclassified failures; the shared Requirement Contract and gate enforcement are required for predictable outcomes.

What's the best way to manage triage routing for parallel workflow execution?

The best way to manage triage routing is enforcing one Execution Mode before delegation, defining a shared Requirement Contract, and applying convergence gates that classify failures against that contract.