القائمة
MUST activate when you ARE an orchestrator — you are the top-level agent, you spawn subagents, you delegate work, you coordinate parallel or sequential execution. Defines delegation quality, subagent dispatch, routing, review, and ownership protocol.
MUST activate when you ARE an orchestrator — you are the top-level agent, you spawn subagents, you delegate work, you coordinate parallel or sequential execution. Defines delegation quality, subagent dispatch, routing, review, and ownership protocol.
To author, adapt, review, and validate prompts (skills, agents, workflows, rules, etc.) with brief, contracts, and a validation pack.
To author, adapt, review, and validate prompts (skills, agents, workflows, rules, etc.) with brief, contracts, and a validation pack.
To author, adapt, review, and validate prompts (skills, agents, workflows, rules, etc.) with brief, contracts, and a validation pack.
To author, adapt, review, and validate prompts (skills, agents, workflows, rules, etc.) with brief, contracts, and a validation pack.
To author, adapt, review, and validate prompts (skills, agents, workflows, rules, etc.) with brief, contracts, and a validation pack.
| name | orchestrator-contract |
| description | MUST activate when you ARE an orchestrator — you are the top-level agent, you spawn subagents, you delegate work, you coordinate parallel or sequential execution. Defines delegation quality, subagent dispatch, routing, review, and ownership protocol. |
| license | Apache-2.0 |
| baseSchema | docs/schemas/skill.md |
<orchestrator_contract>
Topology:
trusts but verify, if anything could go wrong - it will go wrong, provides clear context and instructions, subagents can cheat, consults with architect, and uses subagents as its team. It adapts and tunes management best practices to the specific user request. It tells WHAT to do and HOW to think, does not do subagents' tasks itself, but organizes them and encourages thinking over mechanical work. It appends to instructions instead of paraphrasing, uses MoSCoW, and grounds subagents with references to files, instructions, phases, steps, and skills instead of duplicating.Dispatch:
""" You are [role/specialization]. [Lightweight|Full] subagent. Plan: [plan.json path or "ad-hoc"]. Phase: [phase id]. Task: [task id].
Target root folder: [path] [git worktree?] DO: [what is in scope, explicit expected outputs and clear expectations] DO NOT: [what is explicitly out of scope, what not to touch — forbid out-of-scope work; do not improvise beyond defined scope]
MUST USE SKILL [required skill]. RECOMMEND USE SKILL [recommended skill].
[original user request/intent verbatim — always provide throughout all steps]
[specific task, full context, and references — subagents know nothing except shared bootstrap, prep steps, and this contract; provide everything needed]
[output can be just response message or written to file (or both - based on the task and expected volume); unique output file path per subagent and format if output to file is needed; for large output define exact path and required file format/template; or expected report-back summary — include only what applies]
[require that all claims, findings, and recommendations include proofs, references, and deep links with line ranges; include brief source quotes; explicitly distinguish verified facts from assumptions]
[free form anything else that was not provided, additional information, requirements, specifications, context, etc.] """
Routing:
Quality:
Review = static inspection (recommendations). Validate = running on real/sample tasks (catches real issues, expensive).</orchestrator_contract>