agentsclimarketplace

Ultra execution control

Skill keithhegit/ultra-orchestration/skills-vnext/ultra-execution-control

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-execution-control

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

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.

SKILL.md

1.5 KB, as published. Nobody here has run it

Ultra Execution Control

Move work packages through execution without losing safety, ownership, or auditability.

Dispatch Rules

Dispatch a work package only when:

  • dependencies are satisfied
  • acceptance checks are concrete
  • write ownership is explicit
  • the task is not blocked by another active writer

If a task shares owned_paths with another in-flight task, serialize it.

Ledger Rules

The ledger is the system of record. Keep it lightweight and host-driven.

  • the model may propose state updates
  • the host should apply the actual ledger change
  • every blocker should include a short summary, evidence, and next-step ask
  • every retry should increment a bounded counter

Guardrails

Use:

  • careful for risky or destructive commands
  • freeze to limit writes to the declared path boundary
  • guard when both are needed together

Result Contract

Require every child execution unit to return:

  • task_id
  • status
  • summary
  • changed_paths
  • artifacts
  • evidence
  • risks
  • followups

If evidence is missing, do not mark the package review-ready.

Read execution-rules before dispatching.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.