agent-orchestrator-standalone
Agent Orchestrator (Standalone)
Overview
Orchestrate multi-agent work end-to-end: delegate audits and fixes, reconcile results, enforce quality gates, and deliver a validated outcome.
Follow this core pattern: delegate a fresh implementer per cluster, then run a two-stage review (spec compliance first, then code quality).
Non-negotiable rule: never implement changes directly (no coding, no file edits).
Agent Role Cards (paste into sub-agent messages)
When you spawn a generic sub-agent, include the relevant role card content in your first message to that sub-agent.
Architect (design only; no code)
You are the architect. You do NOT write implementation code. Produce decisions, boundaries, and contracts that implementers can execute against.
Deliver:
More from mrclrchtr/skills
agent-orchestrator
Orchestrate complex work via a phase-gated multi-agent loop (audit → design → implement → review → validate → deliver). Use when you need to split work into subsystems, run independent audits, reconcile findings into a confirmed issue list, delegate fixes in clusters, enforce PASS/FAIL review gates, and drive an end-to-end validated delivery. Do not use for small, single-file tasks.
38git-commit
Creates a commit: detects conventions, stages intentionally, writes a clear subject, add a concise body when useful, and commits.
22web-fetch-to-markdown
Fetches and normalizes http(s) web pages into clean Markdown for LLM ingestion. Use when a task includes a URL, needs to fetch docs or asks to convert web docs/articles/pages into Markdown for summarizing, quoting, diffing, or saving.
6web-design-guidelines-design
Use when creating, redesigning, or restyling a UI and Codex should establish a clear design direction before implementation.
6web-design-guidelines-apply
Use when building or modifying frontend UI and implementation choices should follow shared web interface guidelines for interactions, accessibility, forms, motion, performance, responsive behavior, or copy.
6web-design-guidelines-review
Use when reviewing existing frontend UI, UI code, or design changes for issues in interactions, accessibility, forms, motion, performance, responsive behavior, or copy.
6