# Orchestration > Plan, route, implement, verify, and review substantial work with GPT-6 Astra and dynamically selected native Codex subagents. - Skill: `dannymac180/orchestration` (Agent Skill, multi-file: 4 files) - Install (CLI): `npx skillmds@latest add dannymac180/orchestration` - Raw SKILL.md: https://api.skillmd.com/api/skills/dannymac180/orchestration/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools, Productivity, Security - Author: dannymac180 (https://skillmd.com/u/dannymac180) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/dannymac180/orchestration --- # Astra Advisor Orchestration Act as the architect and acceptance owner. Keep the primary session on GPT-6 Astra at the effort selected by the user. Astra owns intent, architecture, decomposition, delegation decisions, parent verification, and acceptance. A skill cannot change the parent model or effort, and must honor the invocation's effort. If observable runtime metadata says the parent model is not `gpt-6-astra`, report the mismatch as a selection prerequisite and do not claim Astra orchestration. If the model or effort is unobservable, disclose that fact rather than inventing confirmation. After capability preflight and before the first implementation or delegation task call, emit a short, machine-auditable declaration: ~~~text ASTRA ROUTE parent: / delegation: risk: ~~~ Report model and effort as observed evidence. If metadata does not expose a value, say that it is unobservable; never claim a runtime pin that was not confirmed. Read [the operations reference](references/operations.md) before the first delegation. Use the generic `collaboration.spawn_agent` tool only when it is exposed by the current tool schema. Each selected subagent must receive an explicit `model`, an explicit supported `reasoning_effort`, and `fork_turns: none`. Choose dynamically among `gpt-5.6-sol`, `gpt-5.6-terra`, and `gpt-5.6-luna` from the task's risk, context, and independent work available; do not encode a role-to-model mapping or a fixed number of subagents. Give every subagent a concrete, bounded, independent deliverable while Astra continues useful parent work. Do not duplicate the parent's implementation or verification in a subagent. Tools and their public schemas are authoritative. Select only an effort the current tool exposes. If a selected model, effort, spawn control, or required native tool is missing, conflicting, unavailable, or unobservable, fail that delegation closed and continue only with safe parent work or report the limitation. Never silently substitute a model, effort, role, or fabricated tool. Introspection may clarify an omitted runtime field; it cannot replace an available public contract. For a substantial implementation, Astra must inspect the complete diff and rerun the requested checks before starting a fresh read-only review. The reviewer may be any of the three supported subagent models, selected dynamically with explicit model and effort controls. Give it the actual change set and evidence, and require: ~~~text ASTRA REVIEW VERDICT: ship | fix-first | rethink REASON: FINDINGS: RESIDUAL RISK: ~~~ Accept a substantial implementation only after the fresh reviewer returns `ship`. After `fix-first`, the parent applies the correction, verifies again, and obtains a new fresh review. A reviewer remains read-only and never fixes its own findings. Use native Codex subagents in the ChatGPT app when the exposed interface supports the needed controls. Separate app tasks require an explicit user request. For an explicit Codex app task, `mcp__codex_app__create_thread` supports `model` and `thinking`; call `mcp__codex_app__list_projects` first for project targets, using a worktree by default for Git projects and local otherwise. ChatGPT Work cloud `create_thread` must omit `model` and `thinking`, so it cannot currently promise arbitrary model or effort control; do not dispatch a model-pinned request there by default or use an API-key/CLI workaround. Use a future native work tool only when its schema exposes the required controls. ## Live delegation and completion receipts Automatically show a short user-visible lifecycle update for **every** delegation, including reviews, before dispatch and on completion or failure. Before dispatch, include task name, exact bounded ownership, requested model and effort, and the reason for that selection. On return, include agent ID, actual status, and observed model/effort with their evidence source; if unavailable say `unobservable`. If they differ from the request, show both. A submitted request is not runtime confirmation. Keep progress readable; report meaningful changes without polling narration. At the completion of **every task**, even solo, failed, or blocked tasks, emit an `API-EQUIVALENT COST RECEIPT` using the calculator described in the operations reference, or a precise unavailable status when usage cannot be observed. Capture available usage with source, unique call IDs, agent identity, and scope as work runs. Include parent, implementers, and all reviewers before claiming whole-task coverage. Do not invent token counts, missing rates, or success percentages. Unknown is not zero. Distinguish observed tokens from pricing estimates and partial coverage. Show routed USD and the same observed tokens repriced at Astra only when comparable; label the difference a **same-token API price comparison**, never measured all-Astra behavior, actual net task savings, subscription charges, or improved quality/speed. If parent usage is missing, label any available delegated-only comparison separately. With no subagents there are no delegation savings. Effort is metadata, not a price multiplier. Use the versioned snapshot and disclose its date and promotional Sol pricing. Reject unsupported pricing regimes rather than silently using standard rates. An illustrative fixture is optional and must remain separate from this task's receipt.