메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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.
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.
| name | deliver-and-retro |
| description | 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. |
Package the run for the user and for future runs.
final_deliverableorchestration_logvetter_reportcontrol_surface_usedvetter_report.STRICT and STRICT_OPENSPEC, do not deliver unless run ledger,
contract validation, review, and QA status are explicit.Include:
run_modeused_openspec_changeused_openspec_bridgeused_run_ledgerused_contract_validationused_slice_dagused_dynamic_qa