Ultra delivery

Skill keithhegit/ultra-orchestration/skills-vnext/ultra-delivery

Ultra Orchestration 是一套开源的 AI 工程编排技能体系。它将 OpenSpec 规格主线（Program → Milestone → Change → Slice）与 Ultra-Orchestrator 执行阶段（Intake → Plan → Dispatch → Execute → Review → QA → Deliver → Retro）结合，提升交付稳定性与可审计性。

Install

npx -y skills add keithhegit/ultra-orchestration --skill ultra-delivery

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

1.6 KB, as published. Nobody here has run it

Ultra Delivery

Package the run into an auditable user-facing result. This skill is the vNext replacement for the stable deliver-and-retro skill.

Delivery Gate

Do not deliver until:

accepted work packages are reviewed
QA status is explicit
risk decisions are recorded
evidence exists for every major claim
unresolved risks are named

If evidence is missing, route back to ultra-review or ultra-qa.

Required Run Output

Every delivery must include:

final_deliverable
orchestration_log
vetter_report

Recommended additions:

qa_summary
changed_paths
verification_evidence
residual_risks
followups
retro

Final Response Standard

Keep the user-facing final response concise, but do not hide risk.

Mention:

what was completed
where the important artifacts live
what verification passed
what was not verified
what remains as follow-up

Retro

Retro improves the next run and should not block delivery unless it reveals a missing review, QA, or risk gate.

Capture:

which decomposition worked
which guardrails helped
which handoff was noisy or oversized
which contract field should be tightened
whether the vNext skill sequence should change next time

Read delivery-checklist for the final gate.