Skill

amoa-orchestration-guardrails

Enforces orchestrator boundaries, rules, and delegation patterns in AI Maestro. Validates RULE 14/15 compliance, detects violations, and generates checklists/reports.

Github

ai-ml

automation

npx claudepluginhub emasoft/ai-maestro-orchestrator-agent

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Enforces orchestrator boundaries: no implementation, immutable requirements, delegation rules, and communication protocols.

Supporting Assets

references/agent-selection-guide-part1-language-agents.mdreferences/agent-selection-guide-part2-specialized-agents.mdreferences/agent-selection-guide-part3-decision-selection.mdreferences/agent-selection-guide-part4-patterns-practices.mdreferences/agent-selection-guide-part5-advanced.mdreferences/agent-selection-guide.mdreferences/delegation-checklist.mdreferences/non-blocking-patterns.mdreferences/orchestrator-exclusive-communications.mdreferences/orchestrator-guardrails-part1-role-and-actions.mdreferences/orchestrator-guardrails-part2-decision-trees.mdreferences/orchestrator-guardrails-part3-scenarios.mdreferences/orchestrator-guardrails-part4-violations-and-examples.mdreferences/orchestrator-guardrails.mdreferences/orchestrator-no-implementation.mdreferences/progress-monitoring.mdreferences/rule-14-enforcement.mdreferences/sub-agent-role-boundaries-template.mdreferences/user-requirements-immutable.mdreferences/verification-loops.md

SKILL.md

Similar Skills

orchestrator-discipline

Enforces orchestrator discipline in Claude Code multi-agent workflows via PreToolUse hooks gating file reads, diagnostic commands, and bash misuse to prevent context waste.

1 file

orchestrator-discipline

delegation

407

Provides protocols, templates, and rules for constructing subagent delegation prompts with context chains, protocol injection, and downstream declarations in agent orchestration.

2 files

maestro

multi-agent-task-orchestrator

37.1k

Routes tasks to specialized AI agents with anti-duplication checks via task registry, quality gates, and 30-minute heartbeat monitoring. Use for coordinating 3+ agents on complex tasks.

antigravity-awesome-skills

Stats

Stars10

Forks0

Last CommitApr 3, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Orchestration Guardrails Skill

Overview

Enforces orchestrator boundaries: no implementation, immutable requirements, delegation rules, and communication protocols.

Prerequisites

AI Maestro running, GitHub CLI (gh) authenticated.

Output

Guardrail validation reports, rule violation alerts, delegation checklists.

Instructions

Before any action, run self-check from orchestrator-no-implementation.md
Verify requirements are immutable per rule-14-enforcement.md
Ensure all communication flows through orchestrator per orchestrator-exclusive-communications.md
Use delegation-checklist.md for task handoff validation

Copy this checklist and track your progress:

Self-check: am I implementing or delegating?
Requirements immutable (RULE 14)?
Communication via orchestrator only?
Delegation checklist complete?

Examples

Input: Orchestrator about to run npm test directly. Output: RULE 15 violation detected -- delegate testing to worker agent instead.

Error Handling

Rule violation detected: stop, reassess, delegate to worker agent.

Resources

orchestrator-no-implementation.md
- 1. Core Principle
  - 1.1 What the Orchestrator Does
  - 1.2 Why This Rule Exists
- 1. Forbidden Actions for Orchestrators
  - 2.1 Actions That Violate RULE 15
- ...
user-requirements-immutable.md
- 1. Core Principle
  - 1.1 What Immutable Requirements Means
  - 1.2 Why This Rule Exists
- 1. Orchestration Requirement Enforcement
  - 2.1 At Project Start
- ...
rule-14-enforcement.md
- 1.1 Core Rule
- 1.2 Detecting Deviations
- 1.3 When Technical Constraints Conflict
- 1.4 Requirement Compliance Documentation
- Requirement Compliance
- ...
orchestrator-exclusive-communications.md
- 1. Core Principle
  - 1.1 What This Rule Means
  - 1.2 Why This Rule Exists
- 1. Orchestrator-Exclusive Actions
  - 2.1 Actions ONLY the Orchestrator Can Perform
- ...
orchestrator-guardrails.md
- Part 1: Role Definition and Action Classification
- Part 2: Decision Trees
- Part 3: Common Scenarios
- Part 4: Violation Detection and Examples
- Quick Reference Summary
- ...
non-blocking-patterns.md
- Overview
- RULE 17: Orchestrator Must Remain Responsive (IRON RULE)
- 1. Async Task Delegation Patterns
  - 1.1 Background Bash Pattern
  - 1.2 Task Agent with Timeout
- ...
delegation-checklist.md
- 1.0 General Delegation Checklist
  - Pre-Delegation Requirements
  - Delegation Document Contents
  - Post-Delegation Actions
- 2.0 Infrastructure Tasks
- ...
workflow-checklists.md
- Table of Contents (Use-Case Oriented)
- Checklist: Receiving New Task
- Checklist: Delegating Task
- Checklist: Monitoring Delegated Task
- Checklist: Verifying Task Completion
- ...
sub-agent-role-boundaries-template.md
- YAML Frontmatter Structure
- Purpose Section
- Purpose
- Purpose
- Role Boundaries with Orchestrator Section
- ...

Orchestration Guardrails Skill

Overview

Enforces orchestrator boundaries: no implementation, immutable requirements, delegation rules, and communication protocols.

Prerequisites

AI Maestro running, GitHub CLI (gh) authenticated.

Output

Guardrail validation reports, rule violation alerts, delegation checklists.

Instructions

Before any action, run self-check from orchestrator-no-implementation.md

Verify requirements are immutable per rule-14-enforcement.md

Ensure all communication flows through orchestrator per orchestrator-exclusive-communications.md

Use delegation-checklist.md for task handoff validation

Copy this checklist and track your progress:

Self-check: am I implementing or delegating?

Requirements immutable (RULE 14)?

Communication via orchestrator only?

Delegation checklist complete?

Examples

Input: Orchestrator about to run npm test directly. Output: RULE 15 violation detected -- delegate testing to worker agent instead.

Error Handling

Rule violation detected: stop, reassess, delegate to worker agent.

Resources

orchestrator-no-implementation.md

1. Core Principle
- 1.1 What the Orchestrator Does
- 1.2 Why This Rule Exists
1. Forbidden Actions for Orchestrators
- 2.1 Actions That Violate RULE 15
...

user-requirements-immutable.md

1. Core Principle
- 1.1 What Immutable Requirements Means
- 1.2 Why This Rule Exists
1. Orchestration Requirement Enforcement
- 2.1 At Project Start
...

rule-14-enforcement.md

1.1 Core Rule
1.2 Detecting Deviations
1.3 When Technical Constraints Conflict
1.4 Requirement Compliance Documentation
Requirement Compliance
...

orchestrator-exclusive-communications.md

1. Core Principle
- 1.1 What This Rule Means
- 1.2 Why This Rule Exists
1. Orchestrator-Exclusive Actions
- 2.1 Actions ONLY the Orchestrator Can Perform
...

orchestrator-guardrails.md

Part 1: Role Definition and Action Classification
Part 2: Decision Trees
Part 3: Common Scenarios
Part 4: Violation Detection and Examples
Quick Reference Summary
...

non-blocking-patterns.md

Overview
RULE 17: Orchestrator Must Remain Responsive (IRON RULE)
1. Async Task Delegation Patterns
- 1.1 Background Bash Pattern
- 1.2 Task Agent with Timeout
...

delegation-checklist.md

1.0 General Delegation Checklist
- Pre-Delegation Requirements
- Delegation Document Contents
- Post-Delegation Actions
2.0 Infrastructure Tasks
...

workflow-checklists.md

Table of Contents (Use-Case Oriented)
Checklist: Receiving New Task
Checklist: Delegating Task
Checklist: Monitoring Delegated Task
Checklist: Verifying Task Completion
...

sub-agent-role-boundaries-template.md

YAML Frontmatter Structure
Purpose Section
Purpose
Purpose
Role Boundaries with Orchestrator Section
...