Menu
Render Delivery Graph status as a kanban-style report with ready nodes, blockers, validation gaps, and tracker sync state.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Capture reusable learning from completed Delivery Graph nodes, tracks, or demands.
Drive a raw demand all the way to done from a single command - design, plan, and evidence-gated execution - stopping only at two judgment gates and on genuine failure or ambiguity.
Design a structured demand from a raw request, including its gap register, requirements, and acceptance criteria for Delivery Graph Engineering.
Drive the ready queue end to end - implement each ready node, gate it on evidence, and stop on the first failure.
Convert DGE requirements into tracks, dependency nodes, and validation contracts.
Independently verify a Delivery Graph node against its validation contract and block completion until evidence and verifier independence exist.
| name | dge-status |
| description | Render Delivery Graph status as a kanban-style report with ready nodes, blockers, validation gaps, and tracker sync state. |
| argument-hint | [optional graph path] |
Use this skill to inspect graph health.
Show the current operational state of a delivery graph without changing it.
delivery-graph/graph.json.delivery-graph/reports/status-<timestamp>.md.When local tooling is available, use:
npx dge status
npx dge status --save
npx dge status --out delivery-graph/reports/status.md
The status output must include missing validation evidence.
Follow the shared output convention (see skills/README.md): lead with a bold
one-line synthesis of graph health (e.g. "N ready, M blocked, K validation gaps"),
then the sections:
Then a ## Next block with the recommended next command.