agentsclimarketplace

Decision complete planner

Skill keithhegit/ultra-orchestration/skills/decision-complete-planner

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 decision-complete-planner

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

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.

SKILL.md

1.6 KB, as published. Nobody here has run it

Decision Complete Planner

Produce a plan another agent can execute without filling in key decisions.

In mainline STRICT or STRICT_OPENSPEC runs, planning must produce JSON-ready artifacts. Markdown summaries may explain the plan, but they do not replace the machine-checkable TaskManifest and WorkPackage objects.

Produce

  • Short summary
  • Ordered implementation phases
  • JSON TaskManifest entries
  • JSON WorkPackage entries
  • Parallel vs serial execution boundaries
  • Acceptance checks per package
  • Retry budget assumptions for each non-trivial work package
  • Current OpenSpec change and slice status when STRICT_OPENSPEC applies

Use canonical field names from ../ultra-orchestrator/references/contracts.md.

Rules

  • Prefer behavior-level decomposition over file-by-file decomposition.
  • Mark shared write scope explicitly.
  • Treat shared write scope as a write-lock conflict, not a soft warning.
  • Keep non-goals visible.
  • If a design choice is still unresolved, surface it instead of hiding it in prose.
  • For development tasks, prefer one bounded OpenSpec change and one current slice before dispatch.
  • Do not send work to dispatch if artifact validation cannot be planned.

Hand off

Send the plan to $spec-review for completeness, then to $dispatch-and-track.

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.