agent-orchestration-governance
Skill40 starsChanged 4 days agoApache-2.0View on GitHub
Use when changing repository engineering agents, subagent concurrency or depth, delegation policy, or handoff verification rules in hushh-research.
In this repository69 other files it gives its agents.
- AGENTS.mdAGENTS.md
- hushh-webapp/AGENTS.mdAGENTS.md
- impeccableSkill
- analytics-observability-governanceSkill
- animateSkill
- animation-vocabularySkill
- apple-designSkill
- autonomous-rca-governanceSkill
- backend-agents-operonsSkill
- backend-api-contractsSkill
- backend-runtime-governanceSkill
- backendSkill
- brandkitSkill
- client-env-paritySkill
- codex-skill-authoringSkill
- comms-communitySkill
- context-refreshSkill
- contributor-onboardingSkill
- docs-governanceSkill
- emil-design-engSkill
- find-animation-opportunitiesSkill
- founder-brief-curationSkill
- frontend-architectureSkill
- frontend-cache-coherenceSkill
- frontend-design-systemSkill
- frontend-native-surface-mapperSkill
- frontendSkill
- frontend-surface-placementSkill
- future-plannerSkill
- github-contribution-governanceSkill
- hushh-consent-mcpSkill
- hushh-icon-themeSkill
- iam-consent-governanceSkill
- imagegen-frontend-mobileSkill
- imagegen-frontend-webSkill
- improve-animationsSkill
- industrial-brutalist-uiSkill
- kai-test-account-resetSkill
- less-text-karma-jiSkill
- mcp-developer-surfaceSkill
- mobile-nativeSkill
- mobile-parity-auditSkill
- mobile-plugin-contractsSkill
- morphy-axSkill
- one-voice-governanceSkill
- oss-license-governanceSkill
- pdf-artifact-generationSkill
- pick-ui-librarySkill
- pkm-upgrade-rehearsalSkill
- planning-boardSkill
- pr-governance-reviewSkill
- profile-uiSkill
- prototypeSkill
- puppy-one-harnessSkill
- quality-contractsSkill
- release-ios-appstoreSkill
- repo-contextSkill
- repo-operationsSkill
- review-animationsSkill
- reviewer-app-testingSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 5 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Avoid overlap with codex-skill-authoring for generic skill taxonomy and repo-context for broad repository intake.
- Distinctive: line 64
Verify that a custom agent is justified.
- Distinctive: line 65
Keep the fleet at the curated sweet spot: broad read-only evidence lanes, not one agent per skill.
- Distinctive: line 67
Keep custom-agent Markdown files thin: role, sandbox, nicknames, root craft/bacterial-architecture inheritance hook, concise instructions, …
- Very specific: line 68
Treat .agents/subagents/*.md as the only authored fleet.
- Distinctive: line 69
Keep wave-1 agents read-only and leave branch switching, writes, approval, merge, deploy, secrets, and final decisions to the …
- Very specific: line 71
Keep global limits bounded at max_threads = 6 and max_depth = 1 unless a later review proves otherwise.
- Distinctive: line 73
Run agent validation, fleet audit, router smoke, canonical-source check, skill lint, and repo/docs governance checks after orchestration …
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Hussh Agent Orchestration Governance Skill
Purpose and Trigger
- Primary scope:
agent-orchestration-governance-intake - Trigger on repo-scoped custom agents, canonical host configuration limits, delegation policy, child handoff contracts, or workflow orchestration changes.
- Avoid overlap with
codex-skill-authoringfor generic skill taxonomy andrepo-contextfor broad repository intake.
Coverage and Ownership
- Role:
owner - Owner family:
agent-orchestration-governance
Owned repo surfaces:
.agents/subagents.agents/config.json.agents/skills/agent-orchestration-governance.agents/workflows/agent-orchestration-governanceAGENTS.mddocs/operations/README.mddocs/operations/coding-agent-mcp.md.agents/routing.agents/instructions.md.agents/README.md
Non-owned surfaces:
repo-contextcodex-skill-authoringrepo-operationsfuture-planner
Do Use
- Adding or tightening repo-scoped custom agents.
- Changing subagent concurrency/depth limits or delegation policy.
- Defining authority boundaries, parent-only actions, or child handoff shape.
- Keeping agents thin and routed through existing owner/spoke skills.
Do Not Use
- Broad repo scans that should start with
repo-context. - Generic skill creation or taxonomy work that belongs to
codex-skill-authoring. - Domain implementation after the correct owner lane is clear.
- Recursive multi-agent expansion beyond bounded defaults without evidence.
Read First
AGENTS.md.agents/skills/agent-orchestration-governance/references/delegation-contract.md.agents/skills/codex-skill-authoring/references/skill-contract.md.agents/skills/codex-skill-authoring/references/truth-first-operating-kernel.mddocs/operations/coding-agent-mcp.md.agents/skills/agent-orchestration-governance/references/anti-rationalization.md
Workflow
- Verify that a custom agent is justified; prefer skills/workflows when role specialization is not needed.
- Keep the fleet at the curated sweet spot: broad read-only evidence lanes, not one agent per skill.
- Preserve the repo-wide delegation checkpoint and truth-first handoff shape in
AGENTS.mdanddelegation-contract.md. - Keep custom-agent Markdown files thin: role, sandbox, nicknames, root craft/bacterial-architecture inheritance hook, concise instructions, and skill routing.
- Treat
.agents/subagents/*.mdas the only authored fleet; no host projections or copies are created. - Keep wave-1 agents read-only and leave branch switching, writes, approval, merge, deploy, secrets, and final decisions to the parent/governor.
- Reject vendor directories and per-host adapters; read
.agentsthrough rootAGENTS.md. Release finished child sessions through supported host controls and verify closure. - Keep global limits bounded at
max_threads = 6andmax_depth = 1unless a later review proves otherwise. - Route product-direction, founder-language, One/Kai/Nav, PKM, voice/action, and PR north-star lanes through the Founder Wiki North-Star Probe when material; repo/wiki divergence is
current_state_vs_north_star_drift. - Run agent validation, fleet audit, router smoke, canonical-source check, skill lint, and repo/docs governance checks after orchestration changes.
Handoff Rules
- Broad repo intake routes to
repo-context. - Generic skill-system authoring routes to
codex-skill-authoring. - CI, deploy, or runtime-governance follow-up routes to
repo-operations. - Future-state agent-lattice planning routes to
future-planner. - Domain implementation routes to the relevant owner skill.
Required Checks
python3 .agents/skills/codex-skill-authoring/scripts/truth_first_smoke.py
python3 .agents/skills/agent-orchestration-governance/scripts/agent_orchestration_check.py
python3 -m py_compile .agents/skills/agent-orchestration-governance/scripts/agent_orchestration_check.py .agents/skills/agent-orchestration-governance/scripts/delegation_router.py .agents/skills/agent-orchestration-governance/scripts/agent_fleet_audit.py .agents/skills/agent-orchestration-governance/scripts/agent_router_smoke.py .agents/skills/agent-orchestration-governance/scripts/subagent_budget.py
python3 .agents/skills/agent-orchestration-governance/scripts/agent_fleet_audit.py --text
python3 .agents/skills/agent-orchestration-governance/scripts/agent_router_smoke.py
./scripts/ci/repo-governance-check.sh
python3 .agents/skills/codex-skill-authoring/scripts/skill_lint.py
./bin/hushh agents auditDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

