orchestrate

Orchestrates multi-step feature delivery through parallel agent waves, verification, and browser checks.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/gmolike/Claude-Template --skill orchestrate-gmolike
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestrate
Source: https://github.com/gmolike/Claude-Template/tree/main/.claude/skills/orchestrate
Command: npx skills add https://github.com/gmolike/Claude-Template --skill orchestrate-gmolike

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating substantial, multi-stage development tasks (features, redesigns, migrations, audits) by hand leads to context overload, file collisions between parallel changes, and unverified results. This Skill provides an executable delivery cycle that delegates work to subagents, enforces quality gates, and requires real browser verification before committing. ## Core Features & Use Cases - Plan-First with Approval Gates: Maps the problem space first, asks critical questions one decision at a time, and requires approval before hard-to-reverse steps. - Parallel Agent Waves: Runs a discovery wave of parallel recon agents returning structured specs, then a build wave with disjoint file ownership, contract-first schemas, and a single composition agent owning shared files. - Adversarial Verification & Green Gate: A dedicated critic agent reviews correctness and design quality, followed by a full typecheck/lint/test gate executed directly, not trusted from agent reports. - Mandatory Visual Browser Check: Serves the built artifact, loads demo data, tests interactions via element references, works around rAF throttling, and captures screenshots before any commit. - Use Case: Implementing a multi-package feature across a Turborepo monorepo — schema package first, parallel feature slices, integration, full green gate, browser inspection, then grouped conventional commits and PR after approval. ## Quick Start Ask the AI to orchestrate the implementation of your multi-step feature or redesign, describing the task in one sentence after the /orchestrate command.

Frequently Asked Questions about orchestrate

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

FAQPage Schema
How do I coordinate multiple AI agents on a large feature implementation?

Use a wave-based orchestration pattern: a discovery wave of parallel recon agents maps subsystems into structured specs, then a build wave implements features in disjoint directories with a single composition agent owning shared files. This prevents file collisions and keeps the main context free of raw file dumps.

How to prevent file conflicts when running parallel coding agents?

Assign each build agent exclusive ownership of its own directory or slice, and designate exactly one composition agent for shared files and barrel exports. Land the shared schema or contract package first so feature agents build against stable interfaces.

When should I use orchestrated delivery versus simple scaffolding?

Use orchestrated delivery for multi-step features, redesigns, migrations, and broad audits that span multiple packages. For scaffolding a single feature slice, a simpler single-purpose scaffolding skill is more appropriate.

Why do browser animations freeze during automated UI testing?

Chrome throttles requestAnimationFrame in hidden or occluded automation tabs, so count-up and entrance animations freeze at zero even though the data is correct. Work around it with a setTimeout shim and a visibilitychange toggle, or read final values from aria attributes.

What checks should run before committing AI-generated code?

Run the full typecheck, lint, and test gate yourself rather than trusting agent reports, then visually inspect the actual built artifact in a browser with demo data loaded. Commit only after approval, grouped by package as conventional commits, and never commit build artifacts.