orchestrated-execution

Orchestrate a 4-phase execution loop with quality gates for software work units.

Updated Feb 22, 2026

Search Tags:#workflow #tdd #orchestration #code execution #quality gates #adversarial review

Ready to run

npx skills add https://github.com/jpeggdev/buildwithjpegg --skill orchestrated-execution-jpeggdev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: orchestrated-execution
Source: https://github.com/jpeggdev/buildwithjpegg/tree/main/plugins/tribunal/skills/orchestrated-execution
Command: npx skills add https://github.com/jpeggdev/buildwithjpegg --skill orchestrated-execution-jpeggdev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a robust, multi-phase process to ensure code implementation is rigorously validated and adversarially reviewed before committing, preventing bugs and ensuring spec adherence.

Core Features & Use Cases

4-Phase Loop: Implements, Validates, Adversarially Reviews, and Commits work units.
Quality Gates: Enforces strict checks for tests, coverage, linting, and type safety.
Adversarial Review: Uses a separate agent to find contract violations, not suggest improvements.
Use Case: When developing a critical new API endpoint, this Skill ensures the code not only works but is thoroughly vetted against its specification and potential failure modes before being merged.

Quick Start

Use the orchestrated-execution skill to implement and validate the next work unit according to its specification.

Frequently Asked Questions about orchestrated-execution

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

FAQPage Schema

How do I enforce TDD and code coverage checks before committing code?▼

To enforce TDD and code coverage before committing, use a 4-phase execution loop that implements, validates, and adversarially reviews work units against strict quality gates. This prevents bugs and ensures spec adherence before merges.

What is an adversarial code review and how does it validate specifications?▼

An adversarial code review uses a separate agent to actively find contract violations against a spec, rather than suggesting improvements. It validates code by rigorously testing potential failure modes during the review phase of execution.

How do I orchestrate work unit decomposition with dependency graphs for reliable execution?▼

Orchestrate work unit decomposition by managing dependency graphs and context persistence within a multi-phase execution loop. This breaks down complex development tasks into validated units, ensuring reliable execution and tracking.

Can I integrate linting and type checking into an automated code execution workflow?▼

Yes, you can integrate linting and type checking as strict quality gates within an automated code execution workflow. The validation phase enforces these checks alongside tests and coverage before a work unit can commit.

What is the best way to prevent bugs when developing a critical new API endpoint?▼

The best way to prevent bugs in a critical API endpoint is running it through a 4-phase loop: implement, validate, adversarially review, and commit. This thoroughly vets code against its specification and failure modes.

Why does my code pass tests but still fail the adversarial review phase?▼

Code can pass tests but fail adversarial review because the review phase checks for spec contract violations using a separate agent. It looks for potential failure modes and specification deviations that standard tests might miss.