メニュー
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.
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.
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.
| name | spec-review |
| description | 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. |
Audit the plan before implementation begins.
Return one of:
approvedapproved_with_followupsrework_requiredUse concise findings with evidence. If the plan is blocked by unresolved decisions, say so directly.