Skip to content

dayfinggg/openai-codex-agent-skills / codex/skills/orchestration

orchestration

Verified

Plan or coordinate explicitly authorized multi-agent work, including worker briefs, model selection, independent workstreams, integration, and review rounds.

Multi-agent orchestration

Create no workers, agent teams, or external model calls unless the user or an applicable instruction explicitly authorizes delegation and the runtime permits it. Read Delegation briefs before dispatching a worker or selecting a different model.

Keep workstreams independent. Give each worker a defined goal, file ownership, limits, and a verifiable finish condition. Agree on shared interfaces before parallel implementation. If the runtime shares one working copy, assign disjoint files and tell workers not to revert changes they did not make. Coordinate heavyweight work that competes for the same machine, database, or service.

Read External worker runtimes when the user chooses a non-native worker or CLI. Read Implementation and review loops when coordinating multiple implementation tickets or follow-up review rounds.

Treat worker reports as claims. Check the changes and evidence that affect the requested outcome, resolve conflicts at the integration point, and run the appropriate combined check. Do not accept commits, messages, deployments, database writes, or other external actions from a worker as authorized unless the user's request covers those actions.

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall