Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nwave-ai/nw-deliver
Orchestrates the full DELIVER wave end-to-end (roadmap > execute-all > finalize).
Passed 11 of 18 test cases with the skill, and 3 of 18 without it.
and 10 more in the full report
10 fixed4 passed either way8 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 setup phase 1.5, we read the project root CLAUDE.md and find '## Development Paradigm' specifies 'functional'. Which crafter agent should be dispatched for Phase 2 TDD implementation, and what testing style is prioritized?
| Checked | Without skill | With skill |
|---|---|---|
| Dispatches @nw-functional-software-crafter for TDD steps | Missed | Passed |
| Defaults to property-based testing when functional paradigm is configured | Passed | Passed |
The instructions your model reads when the skill loads.
Wave: DELIVER (wave 6 of 6)|Agent: Main Instance (orchestrator)|Command: /nw-deliver "{feature-description}"
Code examples in this skill use Python syntax for illustration only. They are NOT prescriptive about target language. nWave is language-agnostic per the "genericity and agnosticism" mandate (2026-05-24).
Before crafting, detect the target project's language from manifest files: package.json → TypeScript/JS; Cargo.toml → Rust; go.mod → Go; pyproject.toml/setup.py/Pipfile → Python; pom.xml/build.gradle → Java/Kotlin; *.csproj/*.fsproj → C#/F#; Gemfile → Ruby; Package.swift → Swift.
When the target language is NOT Python: adapt every code example to target conventions (imports, type system, test-framework idioms, file extensions, directory layout). Project conventions ALWAYS WIN over examples below.
Empirical anchor: skill examples being Python-only caused LLM to emit Python code in greenfield TS project. Fix per F-SKILL-EXAMPLES-LANGUAGE-LEAK. Connects [[feedback_language_adapter_plugin_architecture_2026_05_24]].
Orchestrates complete DELIVER wave: feature description → production-ready code with mandatory quality gates. You (main Claude instance) coordinate by delegating to specialized agents via Task tool. Final wave (DISCOVER > DISCUSS > SPIKE > DESIGN > DEVOPS > DISTILL > DELIVER).
Sub-agents cannot use Skill tool or /nw-* commands. You MUST:
~/.claude/skills/nw-{skill-name}/SKILL.md)Provenance: feature lean-wave-documentation — D2 (schema-typed sections), D10 (one-line expansion descriptions). Tier-1 [REF] sections (always emitted) + Tier-2 EXPANSION CATALOG items (lazy, on-demand) are the two output bands. Implementation details live in code; the wave-delta sections are pointers + structured summaries. Full contract: nWave/skills/nw-density-resolution-contract/SKILL.md.
Under ## Wave: DELIVER / [REF] <Section> headings:
<N> of <M> from the .feature file with timestamptest cases passed, vs 3 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.