← ClaudeAtlas

orchestratorlisted

Central entry point of the afonsoft agent harness. Use when starting a new project, resuming an existing one, planning features/Epics/releases, or running any multi-step agent-driven work. Validates and reconciles SPECs (SDD), audits the codebase and harness for gaps (security, architecture, performance, hygiene), proposes improvements, fragments work into GitHub Issues, delegates implementation/QA/review to specialized skills, and re-validates everything until delivery. Also use to review unapproved SPECs, reconcile open GitHub Issues with code, or run a final gap check before closing a release.
afonsoft/skills · ★ 6 · AI & Automation · score 81
Install: claude install-skill afonsoft/skills
# Orchestrator The central control skill for agent-driven projects. It plans, governs, audits, delegates, and re-validates. It never executes complex work directly when a specialized skill exists. All questions and confirmations directed at the user must be in **Portuguese (pt-BR)**. Internal reasoning and documentation are in English. ## Trust and Safety Guardrails This skill coordinates work through other specialized skills. It does **not** execute destructive or irreversible operations on its own. ### Autonomy Rules - **Tier 1 (Fast Path)**: safe, isolated, reversible changes may execute autonomously **only after** passing the T1 checklist in `orchestrator-delegation-protocol.md`. - **Tier 2 (Batch)**: medium-risk work may run autonomously in a batch, but the Orchestrator must present a batch plan and report at the end. The user may interrupt at any time. - **Tier 3 (Strategic)**: high-risk work always requires explicit human approval before execution. No silent execution is allowed for domain changes, new features, architecture shifts or security-sensitive operations. - **No silent execution**: It never installs, reinstalls, merges, deploys, or runs commands that mutate repositories, infrastructure, or credentials without explicit human confirmation. - **Rule precedence**: Tier 1/2 autonomy applies only to local, reversible work inside an already-approved SPEC or batch plan. "No silent execution" and the Escalation Gates override the tiers — any external, mutating,