ultra-orchestration

Turn a structured intake artifact into a decision-complete plan, task graph, dependency map, owned paths, acceptance checks, expected outputs, and retry assumptions. Use when work spans multiple steps, files, or roles and needs explicit orchestration.

Assemble the final deliverable, orchestration log, vetter report, and concise retrospective for a completed orchestrated run. Use when implementation and review are complete and results need to be packaged clearly.

Assign work packages by role, enforce owned-path boundaries, manage execution state, track retries, blockers, review readiness, and host-driven ledger updates. Use when work is being handed off across phases or subagents.

Bridge OpenSpec change artifacts into Ultra-Orchestrator execution artifacts. Use when a repo follows OpenSpec for proposal, design, tasks, and archive, but execution should remain controlled by Ultra-Orchestrator through TaskManifest, WorkPackage, review, QA, risk gates, and ledger-based orchestration.

Legacy compatibility entry point for the original Ultra Orchestrator flow. Use only when you need the older lightweight stage-based orchestration behavior without the new strict OpenSpec-first control plane.

Primary Ultra Orchestration entry point for strict Codex-controlled engineering runs. Use this single skill for development, bug fixes, OpenSpec work, multi-file implementation, review/QA-heavy tasks, risk-gated work, or any run that needs automatic mode selection, OpenSpec bootstrap, machine-checkable TaskManifest and WorkPackage artifacts, ledger tracking, slice DAG execution, review, QA, delivery evidence, and retro.

Bridge OpenSpec change artifacts into Codex Ultra vNext execution contracts. Use when a repo stores long-lived specs in `openspec/changes` or `openspec/specs`, but execution should still flow through Ultra manifests, work packages, review, QA, ledger tracking, and final delivery rather than replacing Ultra with a separate control plane.

Compatibility and preview alias for the main Ultra Orchestrator strict protocol. Use this single skill to start vNext-style orchestrated runs when users still invoke ultra-vnext-core; it should follow the same run-mode decision, strict OpenSpec preference, ledger, JSON artifact, contract validation, slice DAG, review, QA, delivery, and retro behavior as ultra-orchestrator.

Rigid decision-complete planning for Codex Ultra vNext. Use after intake, brainstorming, or OpenSpec bridge whenever work spans multiple files, roles, phases, or risk boundaries and must be turned into review-ready TaskManifest and WorkPackage artifacts with explicit dependencies, owned paths, acceptance checks, retry assumptions, and serial versus parallel execution rules.

Final delivery packaging for Codex Ultra vNext. Use after review and QA to assemble the final deliverable, orchestration log, vetter report, validation evidence, residual risks, and retro notes so the user can understand what changed, why it changed, how it was verified, and what remains.

Risk classification and approval gating for Codex Ultra vNext. Use before external tools, unfamiliar skills, destructive commands, broad write scopes, credential access, network operations, repository publishing, or any action where safety, reversibility, user approval, or audit evidence matters.

Design-first discovery for Codex Ultra vNext. Use before planning or implementation whenever the request is ambiguous, creative, architecture-sensitive, or likely to span multiple files, workflows, or user-facing behavior. This skill turns a vague idea into an approved spec with one-question-at-a-time clarification, alternative comparison, and an explicit implementation gate.

Dispatch and execution control for Codex Ultra vNext. Use after planning when work packages must be assigned, retries bounded, blockers surfaced, and write-lock safety enforced through DAG readiness, owned-path checks, careful or freeze guardrails, and host-driven ledger updates.

Scenario-based QA for Codex Ultra vNext. Use after implementation or review whenever behavior changed, a bug was fixed, a user flow was introduced, or delivery quality depends on proving happy path, error path, regression, and user-visible outcomes through static reasoning or dynamic execution when available.

Spec and engineering review for Codex Ultra vNext. Use after planning or implementation to check specification fidelity, evidence quality, constraints compliance, regression risk, and whether work should be accepted, rejected back to execution, or escalated back to planning.

Automatically chain intake, planning, spec review, and plan refinement into one orchestrated planning pass, surfacing only decisions that need explicit user approval. Use when the user wants a fast but disciplined planning workflow.

Normalize ambiguous user requests into a structured intake artifact with task description, context, success criteria, constraints, and task type. Use before planning or implementation whenever requirements are incomplete, mixed, or implicit.

Review implementation results for production bugs, regressions, risk, evidence quality, and missing tests before integration. Use after code changes or when validating a worker result against acceptance criteria.

Run scenario-based verification and regression checks for changed behavior, user flows, and bug fixes before delivery. Use after implementation or review whenever behavior changed or user-visible quality matters.

Classify tools, skills, commands, and external actions by risk level and define required approvals or guardrails before execution. Use whenever a run may invoke unfamiliar tooling, destructive actions, broad write scope, or external systems.

Apply careful, freeze, and guard behaviors to dangerous commands, broad edit scope, and high-impact operations. Use when execution needs command warnings, path restrictions, or combined safety guardrails.

Review plans and work packages for specification completeness, hidden assumptions, dependency gaps, interface risks, and acceptance-check quality. Use after planning and before substantial implementation.