orchestration-governance
npx machina-cli add skill victorgrein/spec-crew/orchestration-governance --openclawOrchestration Governance
Purpose
Route user requests to the correct specialist, enforce skill boundaries, and validate outputs before returning results.
Specialist Contracts
| Specialist | Primary purpose | Allowed skills | Permission profile |
|---|---|---|---|
| builder | Build crews, agents, tasks, tools, memory | core-build, tools-expert | normal write/edit |
| flow | Flows, state-management, routing, orchestration, decorators | flows | normal write/edit |
| auditor | Investigation, auditing, validation | core-build, flows, tools-expert | read-only |
| docs | Documentation authoring and maintenance | core-build, flows | write/edit only *.md; bash read-only |
Routing Rules
- Builder keywords: create, build, scaffold, setup, agent, task, crew, tool, memory
- Flow keywords: flow, state, router, routing, orchestration, decorator, @start, @listen, @router
- Auditor keywords: inspect, audit, investigate, trace, root cause, validate, performance analysis
- Docs keywords: docs, readme, guide, documentation, architecture notes, standards
Canonical Command Ownership
/crew init-> builder/crew inspect-> auditor/crew fix-> auditor first, then builder/flow for implementation when needed/crew evolve-> flow/crew docs-> docs
Delegation Pattern
Write plain-language delegation with:
- Goal
- Context and file paths
- Specialist skill constraints
- Deliverables
- Validation criteria
Auditor Rule
Auditor executes read-only analysis and returns:
- findings
- risk assessment
- recommendations
- validation steps
Auditor does not patch files.
Validation Checklist
- Chosen specialist matches intent and ownership
- Delegation includes exact paths and constraints
- Specialist used only allowed skills
- Permission limits are respected
- Output contract is complete and actionable
Supporting Files
- Subagent directory:
references/subagent-directory.md - Delegation patterns:
references/delegation-patterns.md - Question templates:
references/questioning-guide.md - Delegation template:
assets/delegation-template.md
Source
git clone https://github.com/victorgrein/spec-crew/blob/main/templates/shared/skills/orchestration-governance/SKILL.mdView on GitHub Overview
Orchestration governance routes user requests to the correct CrewAI specialist, enforces skill boundaries, and validates outputs before returning results. It defines specialist contracts (builder, flow, auditor, docs), routing rules, and delegation templates to ensure ownership, permissions, and auditability across builds, flows, audits, and documentation.
How This Skill Works
The skill maps intents to specialists using canonical commands and keyword groups (builder, flow, auditor, docs). It enforces permission profiles and allowed skills per contract, and relies on a Delegation Pattern with goal, context, constraints, and deliverables, plus a Validation Checklist to ensure the output is complete and actionable. Audits run read-only analyses and produce findings, risk assessments, and recommendations without patching files.
When to Use It
- Routing a user request to the correct specialist based on ownership.
- Enforcing allowed skills and permission profiles during tasks.
- Delegating complex changes with goal, context, constraints, and a clear deliverable.
- Auditing outputs with read-only analysis before delivery.
- Updating or creating documentation with the docs specialist.
Quick Start
- Step 1: Identify intent and confirm ownership and required skills.
- Step 2: Use routing rules to map to the correct specialist and delegate.
- Step 3: Apply the delegation pattern and run the validation checklist before delivering.
Best Practices
- Verify the chosen specialist matches the request's intent and ownership.
- Include exact file paths and constraints in the delegation.
- Restrict the specialist to only allowed skills and permissions.
- Use the Validation Checklist to ensure outputs are complete and actionable.
- Prefer auditor-based validation for risk analysis before changes.
Example Use Cases
- /crew init routed to the builder to create a new crew, task, and tools.
- Route /crew inspect to the auditor for read-only validation of artifacts.
- Apply /crew fix with auditor first, then builder/flow for implementation.
- Evolve processes with /crew evolve to update flows and state management.
- Update docs with /crew docs to author or revise architecture notes and guides.
