orchestrated-execution
Execute work units through the rigorous 4-phase Metaswarm cycle (Implement -> Validate -> Adversarial Review -> Commit) with independent quality gate enforcement.
npx skills add a5c-ai/babysitter --skill orchestrated-execution --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
- 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`
- Process
- Anti-Patterns (Enforced)
- Agents Used
- Tool Use
What does the orchestrated-execution skill do?
Execute work units through the rigorous 4-phase Metaswarm cycle (Implement -> Validate -> Adversarial Review -> Commit) with independent quality gate enforcement.
How do I install it?
Run `npx skills add a5c-ai/babysitter --skill orchestrated-execution --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From a5c-ai/babysitter, a repository with 1,642 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.