Author and optionally direct-launch a two-node loop-graph run for implementing a product or engineering requirement through verified vertical slices. Use when a requested feature, integration, migration, or behavior change needs multiple rounds, durable acceptance proof, and independent audit. Not for code cleanup, comparing alternatives before choosing, or a one-shot implementation. Do not execute or resume generated runtime node files from this authoring skill.
Scanned 8/30/2026
Install to Claude Code
npx -y skills add levi-qiao/longgraph-skill --skill loop-deliver --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Loop Deliver?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/levi-qiao-loop-deliver)More formats (shields.io, HTML) on the badges page.
---
name: loop-deliver
description: Author and optionally direct-launch a two-node loop-graph run for implementing a product or engineering requirement through verified vertical slices. Use when a requested feature, integration, migration, or behavior change needs multiple rounds, durable acceptance proof, and independent audit. Not for code cleanup, comparing alternatives before choosing, or a one-shot implementation. Do not execute or resume generated runtime node files from this authoring skill.
---
# loop-deliver — a loop-graph preset for requirements
A thin authoring entry. It binds a requirement-delivery pack, starts the owner
interview, then follows [`loop-graph`](../loop-graph/SKILL.md) to compile the normal
executor, ledger, directives, ops, and supervisor artifacts. It is not a second runtime
and it does not ship a second template set.
## Fit check
- Use this when a feature, integration, migration, or behavior change needs several
verified slices and an independent acceptance audit.
- Use [`../loop-converge/SKILL.md`](../loop-converge/SKILL.md) when the goal is code
cleanup or consolidation. Use [`../loop-research/SKILL.md`](../loop-research/SKILL.md)
when the decision between approaches is still open.
- If the requirement fits one normal host task, say so and send it directly. Do not wrap
it in a graph.
## On invoke
1. Inspect the workspace and current host the same way loop-graph does. Never ask which
client this is when context already identifies it.
2. Read and bind [`preset.md`](preset.md). That pack is the North Star, supervisor
requirement, interview, shape, method guards, knob overrides, and artifact emphasis.
Do not redesign them.
3. Start the owner interview immediately. Ask only the pack's unresolved choices —
outcome/acceptance, authority, and launch — as recommended A/B (or A/B/C) choices.
Do not ask the owner to invent a plan.
4. Read and follow [`../loop-graph/SKILL.md`](../loop-graph/SKILL.md) from **When called
from a preset skill** through generate and deliver. Compile only from
loop-graph's [`templates/`](../loop-graph/templates/). This skill never executes the
generated nodes.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!