keithhegit/ultra-orchestration / skills/decision-complete-planner
decision-complete-planner
VerifiedTurn 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.6 KB |
| agents/openai.yaml | config | 281 B |
SKILL.md
View on GitHub---
name: decision-complete-planner
description: 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.
---
# 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`](../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`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |