Skip to content

a5c-ai/babysitter / library/methodologies/metaswarm/skills/orchestrated-execution

orchestrated-execution

Verified

Execute work units through the rigorous 4-phase Metaswarm cycle (Implement -> Validate -> Adversarial Review -> Commit) with independent quality gate enforcement.

FileKindSize
README.mdmarkdown631 B
SKILL.mdskill md1.5 KB
---
name: orchestrated-execution
description: Execute work units through the rigorous 4-phase Metaswarm cycle (Implement -> Validate -> Adversarial Review -> Commit) with independent quality gate enforcement.
allowed-tools: Read, Write, Edit, Bash, Grep, Glob, WebFetch, WebSearch, Agent, AskUserQuestion
graph:
  domains: [domain:software-engineering]
  skillAreas: [skill-area:agentic-loops, skill-area:orchestration-loop]
  workflows: [workflow:feature-development]
  topics: [topic:developer-experience]
  roles: [role:tech-lead, role:backend-engineer]
---

- Executing tasks requiring rigorous quality enforcement
- When TDD compliance must be verified independently

## Process

1. **IMPLEMENT** - Coder executes via TDD against spec with DoD items
2. **VALIDATE** - Orchestrator independently runs tsc, eslint, vitest (never trusts subagent)
3. **ADVERSARIAL REVIEW** - Fresh reviewer checks spec compliance: binary PASS/FAIL with evidence
4. **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 implementation
- `agents/code-reviewer/` - Fresh adversarial review
- `agents/issue-orchestrator/` - Independent validation

## Tool Use

Invoke via babysitter process: `methodologies/metaswarm/metaswarm-execution-loop`
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall