ai-orchestrator
From the author
Build a whole feature end-to-end through subagents. It plans gated checkpoints, writes tests and prototypes, then loops each checkpoint through implement → behavior gate (CLI/code tests, UI e2e last) → UI gate (live vs prototype) → adversarial review gate until every checkpoint passes, then hands it to a human to review. Use when the user says "build X", "orchestrate X", "/ai-orchestrator <feature>", or asks to resume an orchestrated feature.
Install
npx skills add arcasilesgroup/ai-engineering --skill ai-orchestrator -a claude-code
Installs to .claude/skills/ai-orchestrator/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 82
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- ai-agent-orchestrationdatadrivenconstruction/DDC_Skills_for_AI_Agents_in_ConstructionOrchestrate multiple AI agents for construction workflows: estimator, scheduler, document, QA and safety agents coordinated by a supervisor agent, with human checkpoints. Use when automating end-to-end project processes with agentic AI.Testing★ 372
- seo-orchestratorHainrixz/claude-seo-aiOrchestrates a full SEO + AI-search audit — acquires the site with the bundled scripts (crawl/snapshot), detects platform and vertical, runs the deterministic checks, dispatches the read-only specialist subagents in parallel with a dispatch envelope, merges their findings into a persisted report, and presents the two scores. Invoked by the `audit` and `geo` commands; not called directly.Marketing★ 79
- agent-orchestra3338902669-ops/agent-orchestraUse when three or more AI agents are available and a task needs coordinated execution, or when work must be handed to another agent, session or tool. It ships the coordination rules as ENFORCED invariants rather than advice: one writer per resource (a conflicting claim is refused and names the holder), a verifier that is never the implementer and whose PASS must carry criterion-linked evidence, a failed verification that blocks both done and dispatch to evidence, three failed rounds that block the task outright, an external action that cannot be dispatched until an approval covering it is recorded, a domain review by a third party for consequential work, rigorous E1-E4 evidence grading with enforced floors, capability-scored role assignment from a roster of any size (any agent names), a shared handoff record with a checker, a dependency-free task-queue CLI, an important-task intake gate, and a coordination anti-pattern guide. One command - scripts/gate.mjs - runs sixteen checks and injects twelve known faultsWriting★ 93
- ai-test-plannerarcasilesgroup/ai-engineeringPlan and write the tests for a feature, bottom-up. Everything that code or the CLI can verify (pure logic, API endpoints, DB constraints, auth/role rules) is tested without a browser. UI end-to-end tests come last and cover only what the lower layers can't. Use when the user asks to plan tests, write tests, or add test coverage for a feature or checkpoint (e.g. "/ai-test-planner discount rules").Testing★ 61
- oma-orchestratorfirst-fluke/oh-my-agentAutomated multi-agent orchestrator that spawns CLI subagents in parallel, coordinates via MCP Memory, and monitors progress. Use for orchestration, parallel execution, and automated multi-agent workflows.Engineering★ 1.4K
- ai-architectarcasilesgroup/ai-engineeringResearch and advise on the best way to approach a software project, including architecture, tech stack, implementation strategy, pricing/operating-cost tradeoffs, benchmark research, and comparisons with similar real-world projects. When the project hinges on a technical mechanism, it can also run a gated arXiv prior-art deep dive before recommending a path. Use before building, mid-build, or after completion when the user asks for project strategy, optimal approach, research comparables, similar projects, stack selection, vendor/service choice, repo analysis, architecture critique, implementation feedback, a prioritized improvement plan, or asks "has anyone solved this", "what's the state of the art", "check prior art", "how should I build this", or "am I about to rebuild something that already exists". Not for narrow single-bug debugging or isolated file edits — use /ai-debug — nor for deciding what to build — use /ai-orchestrator.Planning★ 61
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in