Orchestration governance
Skill victorgrein/spec-crew/templates/shared/skills/orchestration-governance
Spec Crew is a spec-driven CrewAI toolkit for Claude Code and OpenCode, with canonical commands, agents and skills.
npx -y skills add victorgrein/spec-crew --skill orchestration-governanceAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Governance skill for orchestrating CrewAI specialists with strict ownership, skill boundaries, and execution permissions.
SKILL.md
2.3 KB, 485 tokens by cl100k_base, as published. Nobody here has run it
Orchestration 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