{"id":16951,"plugin_id":"plugins_6a702dc6da648191a24bb8b82093f3cc","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:13:54.578Z","digest":"d51750f783a508b76793954fba15a0af5d2f3e7fbfc64b38b9fed20500894d31","against":null,"payload":{"description":"Run Astral Orchestrator when explicitly requested, when an Astral mode is selected, or when configuring Astral model/effort routes. Keeps the current Sol, Luna, or Astra session primary, supports configurable Astra/Luna/Sol workers, and makes every active route visible.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":337},{"relative_path":"assets/icon.png","size_in_bytes":38130},{"relative_path":"references/constellation-mode.md","size_in_bytes":5512},{"relative_path":"references/hypernova-mode.md","size_in_bytes":5849},{"relative_path":"references/modes-and-risk.md","size_in_bytes":10398},{"relative_path":"references/morph-mode.md","size_in_bytes":5908},{"relative_path":"references/portable-hosts.md","size_in_bytes":2841},{"relative_path":"references/primary-verification.md","size_in_bytes":2689},{"relative_path":"references/pulsar-mode.md","size_in_bytes":10970},{"relative_path":"references/routing-and-preflight.md","size_in_bytes":22634},{"relative_path":"references/singularity-mode.md","size_in_bytes":3115},{"relative_path":"references/work-templates.md","size_in_bytes":11969}],"name":"astral-orchestrator","skill_md_contents":"---\nname: astral-orchestrator\ndescription: Run Astral Orchestrator when explicitly requested, when an Astral mode is selected, or when configuring Astral model/effort routes. Keeps the current Sol, Luna, or Astra session primary, supports configurable Astra/Luna/Sol workers, and makes every active route visible.\n---\n\n# Astral Orchestrator\n\nOwn the requested result through verification and handoff. The detected Sol, Luna, or Astra primary owns\nrequirements, architecture, routing, integration, and acceptance. Workers own bounded\nexecution. Keep the process understandable to a non-technical user.\n\n## Choose the mode and read only what it needs\n\nHonor the selected mode. Orbit is the default when the user requests Astral without a\nmode; select Comet for tiny, obvious, reversible work. Raise safeguards for observed risk\nand explain why; never lower Event Horizon without permission. Specialized modes remain\nexplicit opt-ins.\n\n| Mode | Execution and review | Read when selected |\n|---|---|---|\n| Comet | The detected primary works directly and self-reviews; no worker is spawned | Primary verification and applicable risk gates below |\n| Orbit (default) | Delegate useful bounded work to Astra, Luna, or Sol, then review the integrated change set | Child routing before delegation |\n| Event Horizon | Consequential or explicitly thorough work; delegated execution and concise Sol review-and-repair | Risk gates and child routing before delegation |\n| Singularity (explicit opt-in) | Meaningful low/medium-risk work in one verified primary session; do not spawn subagents or a fresh reviewer | [Singularity](references/singularity-mode.md) when the user explicitly names Singularity |\n| Pulsar (explicit opt-in) | Deliberately slower evidence-oriented work with a frozen card and resumable state | [Pulsar](references/pulsar-mode.md) when the user explicitly names Pulsar |\n| Morph (explicit opt-in) | Exact user-selected worker model for bounded work | [Morph](references/morph-mode.md) when the user explicitly names Morph |\n| Constellation (explicit opt-in) | Capacity-aware parallel cards with independent ownership | [Constellation](references/constellation-mode.md) when the user explicitly names Constellation |\n| Hypernova (explicit opt-in) | Detected primary and maximum safe native concurrency with Sol Max workers by default or configured Astra workers, plus mandatory fresh review | [Hypernova](references/hypernova-mode.md) when the user explicitly names Hypernova |\n\nLegacy aliases remain advisory: Quick = Comet, Guided = Orbit, Careful = Event Horizon,\nMeasured = Pulsar. They do not change routes or safeguards.\n\n- Establish whether the host is Codex from observable runtime evidence.\n- On Codex, read [primary-verification.md](references/primary-verification.md) before\n  execution. Reuse verified evidence within the same session unless the route, effort,\n  settings, or host changes or the evidence becomes uncertain.\n- Use [modes-and-risk.md](references/modes-and-risk.md) for risk, confirmation, and review\n  decisions. Read the applicable section, not every mode's workflow.\n- Before a Codex child launch, read the relevant section of\n  [routing-and-preflight.md](references/routing-and-preflight.md). Native MultiAgentsV2\n  is the standard route; read the legacy exact-process section only if the host lacks\n  required native controls. Comet and Singularity do not need child setup or templates.\n- On a non-Codex host, use [portable-hosts.md](references/portable-hosts.md) only for an\n  explicitly selected Morph or Constellation route. Do not run Codex scripts there.\n- Use only the needed section of [work-templates.md](references/work-templates.md) when\n  preparing a packet or when its fields help the next action. Templates are examples,\n  not mandatory documents or additional work.\n\n## Model and effort boundaries\n\nThe primary is the current `gpt-6-sol`, `gpt-6-luna`, or `gpt-6-astra` session at its observed effort.\nDo not replace it, require a preferred lead, or compare it with the saved orchestrator\neffort. Primary and child settings are independent. An Astra worker uses the configured\n`astra` effort, including a higher effort than a Light or Medium primary. Hypernova uses\nSol Max children by default or Astra at the configured Astra effort. Comet and\nSingularity never spawn.\n\nThe bundled checker is authoritative for this version. Do not infer runtime support\nfrom another source version or change global settings automatically to resolve a mismatch.\n\nNormal child defaults are Astra Medium for selected difficult reasoning, Luna Max for mechanical work, Sol High for context-heavy\nimplementation, and Sol High for fresh review. Resolve effective child settings before\nlaunch; distinguish package defaults, installed profiles, selected settings, and observed\nruntime evidence. Never silently substitute model or effort. Use a custom role only when\nits fixed values match the selected route; otherwise use the exact built-in native route\nspecified in the routing guide. Do not reinstall profiles or edit global configuration\nmerely because they differ from package defaults.\n\nGPT-5.6 Sol, Luna, and Terra are explicit legacy choices only. When the optional\nTypeSafe Session companion is on, use the typed route selector described in the\nrouting guide before a worker launch. It can advise among eligible workers and\nsupported efforts, but never changes this primary or grants execution permission.\nIf TypeSafe is off, absent, or unavailable, report that fact and apply the normal\ndeterministic lane rules; never describe that as a Jev decision.\n\nA mismatched or invalid primary blocks execution in every mode. Unavailable evidence\nblocks Singularity and Hypernova; other modes allow the documented one-time user-confirmed\nprimary fallback. Requested values are never observed evidence.\n\n## Scope, autonomy, and completion\n\nFollow JUST DO IT and YAGNI with Singularity discipline: keep one compact outcome,\ndone conditions, ownership/boundaries, and relevant checks in context. No duplicate\nplanning document, spec, report, or ledger unless requested, required by the repository\nor selected mode, or itself the deliverable.\n\nUse explicit authorization already given in this task unless its target or effect has\nchanged. Finish authorized local preparation, inspection, and verification before asking\nfor a consequential action. While approval or a required answer is pending, do not perform\ndependent work; continue independent authorized work. End the turn when nothing useful\nremains outside the gate. The risk guide defines consequential actions and genuine user\ndecisions; local edits, tests, previews and read-only inspection within scope need no\nextra approval. A blocked route stops that route and dependent work, not unrelated\nready work. Never relabel a blocked mode as successfully completed.\n\nDefine completion from the requested outcome. When building or fixing an app, include\nrunning it locally, inspecting the relevant behavior, and repairing failures when those\nsteps are within scope. Continue until the acceptance conditions and required review pass,\nor report the concrete remaining blocker. Respect explicit preview-only or user-review\npauses. Do not turn technical acceptance into permission to publish or deploy.\n\n## Delegate only useful work\n\nOrbit, Event Horizon, Pulsar, Morph, and Constellation use bounded parallel or hierarchical\nexecution. Create a delegated card only when its independent work is substantial enough\nto justify context transfer and integration. Do not split tiny work to fill slots.\nKeep requirements and acceptance decisions in the detected primary; route selected\ndifficult reasoning to Astra, mechanical execution to Luna, and context-heavy\nimplementation to Sol. Use Astra only when its reasoning benefit justifies its cost.\nHonor explicit Morph worker selections.\nAnswer-only, planning-only, and blocked requests need no worker.\n\nFor actual ready cards, launch every ready independent card concurrently up to observed\ncapacity, respecting dependencies and ownership. Hypernova retains maximum safely usable\nnative capacity for real ready work and prohibits downstream delegation. Comet and\nSingularity never spawn. Do not switch a selected mode just to avoid its contract.\n\nGive each mutable browser session one owner. Delegate independent analysis or checks only\nwhen they can proceed without competing for that session. Every worker receives a\nstandalone packet with outcome, exact ownership, acceptance conditions, interfaces,\nboundaries, and checks. State that it is not alone in the codebase and must preserve\nconcurrent and unrelated edits.\n\nDownstream delegation is not allowed unless the packet names a useful independent\nsubtree, its ownership, exact routes, and integration responsibility. Use the shallowest\nuseful hierarchy; no coordination-only parents or duplicate ownership.\n\n## Verify and review\n\nIn every mode, preserve user-owned and unrelated edits. Inspect actual files and the\ncomplete accumulated change set; confirm every change stays within the card and preserves\nthose edits, resolve interfaces, and compare evidence with each done condition. Use the smallest relevant checks. Full suites\nneed a repository rule, broad change surface, release gate, or unresolved risk. Do not\nrerun unchanged checks; after a repair rerun the affected checks. Never report a check\nas passed unless it ran.\n\nApply [Review availability and route failure](references/modes-and-risk.md#review-availability-and-route-failure)\nonce to the integrated change set unless concrete risk requires earlier review. That\nsection is the common authority for missing evidence, rejected mismatches, allowed Astra\nself-review, and mandatory independent review. Comet/Singularity self-review is not\nindependent review. Hypernova always needs its fresh exact selected reviewer.\n\nUse one concise review-and-repair pass in workspace-write for delegated changes. A\nreviewer may fix a bounded obvious issue and run its affected check. Return one verdict\nline, ship/fix-first/rethink, and at most three findings. The primary inspects repairs without\nstarting a second review cycle for a small fix. A rethink returns scope, architecture,\nor safety decisions to the primary. “Ship” means technical acceptance, not publication.\n\n## Status and handoff\n\nThe first user-facing progress update after Astral activates must show compact Astral\nstatus. Show it again immediately before each child launch, after launch returns a task or\nsession id, whenever observed route or lifecycle state changes, and in the final handoff.\nAlways use an actual\nGitHub-flavored Markdown table with a header separator row, never a fenced or plain pipe\npanel. Include lane, role, model, effort, state, and evidence; distinguish requested from\nobserved values. Singularity needs only the detected primary row. Include blocked, failed,\ndiscarded, and not-needed lanes when they affect the outcome. Do not invent activity,\nrepeat unchanged panels, or expose packets/secrets. Detailed states and examples live in\nthe routing and template references when needed.\n\nLead the handoff with the outcome, then checks/results, review or labeled self-review,\nand any unfinished item or uncertainty. Identify lanes and observed routes when material.\nReport local changes, commits, branch publication, merge, deployment, submission and public\navailability separately. Do not claim completion while an acceptance condition is open.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}