Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nwave-ai/nw-deliver-orchestration
DELIVER wave orchestration workflow -- 9 phases from baseline to finalization. Load when user invokes *deliver command. Covers state tracking, smart skip logic, retry, resume, and quality gate enforcement.
Passed 15 of 21 test cases with the skill, and 6 of 21 without it.
and 9 more in the full report
10 fixed6 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
During Phase 5-6, individual step files are created from the roadmap. Which specific reviewer role is responsible for reviewing each step file?
| Checked | Without skill | With skill |
|---|---|---|
| Assigns @nw-software-crafter-reviewer to review per-step files. | Missed | Passed |
The instructions your model reads when the skill loads.
When invoked via *deliver "{feature-description}", Apex orchestrates the complete DELIVER wave lifecycle.
Parse feature description, derive feature ID, execute 9 phases in order. Track state for resume capability.
Invocation: *deliver "Implement user authentication with JWT tokens"
Create: docs/feature/{feature-id}/deliver/baseline.yaml. Reviewer: @nw-software-crafter-reviewer.
Smart skip: yes (if file exists AND validation.status == "approved").
Create: docs/feature/{feature-id}/deliver/roadmap.json.
Reviewer 1: @nw-product-owner-reviewer (business) | Reviewer 2: @nw-software-crafter-reviewer (technical). Sequential reviews.
Smart skip: yes (if approved).
Define steps in: docs/feature/{feature-id}/deliver/roadmap.json. Reviewer: @nw-software-crafter-reviewer (per roadmap step).
Smart skip: yes (if all approved).
For each step: invoke @nw-software-crafter with step ID. Automatic dependency ordering (topological sort via Kahn's algorithm). 11-phase TDD per step (PREPARE through COMMIT). Local commit after each step (no push). Stop immediately if any step fails.
Archive to: docs/evolution/{timestamp}_{feature-id}.md. Clean up workflow files.
Display comprehensive statistics | List all quality gates passed | Show next steps (review evolution doc, push commits, proceed to DEVOPS wave validation).
validation.status == "approved" -> skip creation, load for contexttest cases passed, vs 6 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.