agentsclimarketplace

Subagent orchestration

Skill ArcanEdge-AI/codex-agent-playbook/skills/subagent-orchestration

Tool-agnostic custom instructions, subagent playbooks, skills, and reference docs for production-grade Codex coding agents.

Install
npx -y skills add ArcanEdge-AI/codex-agent-playbook --skill subagent-orchestration

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 28 days oldThe repository was created 28 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 1 stars1 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

Use when a coding task may benefit from Codex subagents for planning, engineering, review, testing, or documentation lookup. Helps the main agent delegate bounded work and verify outputs before accepting them.

SKILL.md

2.0 KB, as published. Nobody here has run it

Subagent Orchestration Skill

The main agent is the senior developer and orchestrator. Subagents assist but do not own the outcome.

Use this skill when:

  • the task is complex, multi-file, risky, or ambiguous
  • a Planner could improve the work sequence or validation strategy
  • an Engineer can safely handle a bounded implementation slice
  • a Reviewer can inspect a diff or design for correctness and risk
  • a Tester can analyze failing checks, logs, flakes, or validation gaps
  • Docs can verify repository, framework, library, API, or platform behavior

Do not use this skill when:

  • the task is trivial
  • one coherent design judgment is required
  • requirements are materially unclear
  • subagents would edit the same files
  • the main agent cannot verify the result

Workflow:

  1. Clarify the task goal and success criteria.
  2. Decide which work, if any, should be delegated.
  3. Choose from the Codex roles: Planner, Engineer, Reviewer, Tester, and Docs.
  4. Right-size the model when model selection is available:
    • use cheaper or faster models for bounded, low-risk, easily verifiable work
    • use stronger reasoning for planning, implementation strategy, meaningful review, ambiguous debugging, security-sensitive work, and high-impact changes
  5. Give each subagent a precise assignment:
    • role
    • goal
    • context
    • model / reasoning guidance
    • scope
    • non-goals
    • permissions
    • required evidence
    • output format
  6. Wait for delegated results before accepting conclusions.
  7. Verify subagent claims against primary evidence.
  8. Inspect any changed files yourself.
  9. Accept, reject, or revise subagent recommendations.
  10. Report relevant subagent usage in the final response.

Never accept a subagent's conclusion solely because it sounds confident.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.