orchestrate-engineering SKILL.md skillA
orchestrate-engineering from phelan164/codex-howto is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add phelan164/codex-howto/orchestrate-engineering@git:20260724.a8a7148Pins git:20260724.a8a7148 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- phelan164/codex-howto
- Path
skills/orchestrate-engineering/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260724.a8a7148, committed Jul 24, 2026
- Size
- 3,956 bytes
- Repository stars
- 20
- License
- MIT
Coordinate complex engineering work across bounded subagents while protecting the main context, preventing edit conflicts, and measuring whether delegation was worthwhile. Use when the user asks to delegate, parallelize, orchestrate, use subagents, fan out a review, or handle a large task with independent workstreams; do not use for small, tightly coupled, or inherently sequential tasks.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Orchestrate Engineering ## Start with the delegation decision 1. Read applicable `AGENTS.md` files and the task’s acceptance criteria. 2. Map dependencies before creating workers. 3. Use one agent when the task is small, tightly coupled, or dominated by shared-file edits. 4. Delegate only when at least two workstreams are genuinely independent, noisy investigation should be isolated, or specialized review materially improves coverage. 5. Explain the chosen topology briefly before starting workers. Subagents normally consume more total tokens than a comparable single-agent run. Optimize for fewer failed loops, cleaner context, better coverage, or lower elapsed time—not the highest agent count. ## Choose a topology - Use **fan-out/fan-in** for independent read-only research, review, triage, or log analysis. - Use a **pipeline** when exploration, planning, implementation, testing, and review depend on prior outputs. - Use **partitioned implementation** only after shared interfaces are stable and each worker owns exclusive files or subsystems. …
Read the whole file at its exact version.
How to install
mdr add phelan164/codex-howto/orchestrate-engineering@sha256:5f9b767477217897The line at the top of this page pins the label git:20260724.a8a7148, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_wj6opz34lybjl63e)
8 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jul 24, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3956 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
phelan164/codex-howto · 20 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_wj6opz34lybjl63e GET https://markdownregistry.com/api/v1/resolve?ref=phelan164/codex-howto/orchestrate-engineering GET https://markdownregistry.com/api/v1/blob/5f9b767477217897d35b2f712b52e38598c645f0a2b8eafd3f2c07dd5335b724
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.