orchestrated-execution
Scannednpx machina-cli add skill a5c-ai/babysitter/orchestrated-execution --openclawOrchestrated Execution
Overview
Execute work units through the Metaswarm 4-phase cycle. Quality gates are blocking state transitions. Adversarial reviews use fresh reviewers with binary PASS/FAIL verdicts.
When to Use
- Implementing work units from an approved plan
- Executing tasks requiring rigorous quality enforcement
- When TDD compliance must be verified independently
Process
- IMPLEMENT - Coder executes via TDD against spec with DoD items
- VALIDATE - Orchestrator independently runs tsc, eslint, vitest (never trusts subagent)
- ADVERSARIAL REVIEW - Fresh reviewer checks spec compliance: binary PASS/FAIL with evidence
- COMMIT - Only after adversarial PASS, within declared file scope
Anti-Patterns (Enforced)
- Self-certifying (trusting subagent "tests passed" claims)
- Combining phases into single steps
- Reusing reviewers after FAIL
- Passing previous review findings to new reviewers
- Treating quality gate failures as advisory
Agents Used
agents/coder/- TDD implementationagents/code-reviewer/- Fresh adversarial reviewagents/issue-orchestrator/- Independent validation
Tool Use
Invoke via babysitter process: methodologies/metaswarm/metaswarm-execution-loop
Source
git clone https://github.com/a5c-ai/babysitter/blob/main/plugins/babysitter/skills/babysit/process/methodologies/metaswarm/skills/orchestrated-execution/SKILL.mdView on GitHub Overview
Orchestrated Execution drives work units through the Metaswarm 4-phase cycle: Implement, Validate, Adversarial Review, and Commit. It enforces independent quality gates and uses fresh reviewers to deliver binary PASS/FAIL verdicts.
How This Skill Works
Coders implement against the spec using TDD and DoD items. The Orchestrator then runs independent validations (tsc, eslint, vitest) without trusting subagents. A fresh adversarial reviewer assesses compliance and returns a binary PASS/FAIL with evidence; commit occurs only after a PASS within the declared file scope.
When to Use It
- Implementing work units from an approved plan
- Executing tasks requiring rigorous quality enforcement
- When TDD compliance must be verified independently
- Handling changes that require independent validation before merge
- Reworking components with enforced gate transitions
Quick Start
- Step 1: Implement via TDD against the spec and DoD items.
- Step 2: Run the independent validations (tsc, eslint, vitest) with the orchestrator.
- Step 3: Have a fresh adversarial reviewer assess with a binary PASS/FAIL and evidence; if PASS, commit within the declared file scope.
Best Practices
- Enforce independent quality gates between phases to block state transitions
- Use fresh adversarial reviewers for the review phase
- Never trust subagent test results; rely on independent validation
- Keep phases explicit and non-overlapping; avoid combining steps
- Commit only after adversarial PASS within declared file scope
Example Use Cases
- A developer implements a new feature with TDD, then runs the Metaswarm Validate phase (tsc, eslint, vitest) before an adversarial reviewer confirms compliance and the code is committed.
- A bugfix is delivered through metaswarm with isolated scope, fresh reviewer, binary verdict, and then commit.
- Refactoring a module is performed with independent validation and adversarial review to ensure no behavioral changes.
- Onboarding a new project, features are added via metaswarm to enforce strict quality gates before merge.
- Cross-team changes are coordinated by the issue orchestrator to ensure gates pass before merge.
