Feature Planner
serendipity1004/cc-feature-implementer
Creates phase-based feature plans with quality gates and incremental delivery structure.
DELIVER wave orchestration workflow -- 9 phases from baseline to finalization.
Install Nw Deliver Orchestration
$ npx skills add nWave-ai/nWave --skill nw-deliver-orchestration -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nWave-ai/nWave nw-deliver-orchestration --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/nWave-ai/nWave.git skills-src && mkdir -p .claude/skills && cp -r skills-src/nWave/skills/nw-deliver-orchestration .claude/skills/nw-deliver-orchestration && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "nw-deliver-orchestration" agent skill from https://github.com/nWave-ai/nWave/tree/main/nWave/skills/nw-deliver-orchestration into .claude/skills/nw-deliver-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nw-deliver-orchestration", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/nWave-ai/nWave/tree/main/nWave/skills/nw-deliver-orchestrationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add nWave-ai/nWave --skill nw-deliver-orchestration -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nWave-ai/nWave nw-deliver-orchestration --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nWave-ai/nWave.git skills-src && mkdir -p .agents/skills && cp -r skills-src/nWave/skills/nw-deliver-orchestration .agents/skills/nw-deliver-orchestration && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "nw-deliver-orchestration" agent skill from https://github.com/nWave-ai/nWave/tree/main/nWave/skills/nw-deliver-orchestration into .agents/skills/nw-deliver-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nw-deliver-orchestration", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nWave-ai/nWave --skill nw-deliver-orchestration -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nWave-ai/nWave nw-deliver-orchestration --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nWave-ai/nWave.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/nWave/skills/nw-deliver-orchestration .cursor/skills/nw-deliver-orchestration && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "nw-deliver-orchestration" agent skill from https://github.com/nWave-ai/nWave/tree/main/nWave/skills/nw-deliver-orchestration into .cursor/skills/nw-deliver-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nw-deliver-orchestration", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/nWave-ai/nWave.git --path nWave/skills/nw-deliver-orchestration--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add nWave-ai/nWave --skill nw-deliver-orchestration -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nWave-ai/nWave nw-deliver-orchestration --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nWave-ai/nWave.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/nWave/skills/nw-deliver-orchestration .gemini/skills/nw-deliver-orchestration && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "nw-deliver-orchestration" agent skill from https://github.com/nWave-ai/nWave/tree/main/nWave/skills/nw-deliver-orchestration into .gemini/skills/nw-deliver-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nw-deliver-orchestration", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install nWave-ai/nWave nw-deliver-orchestrationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add nWave-ai/nWave --skill nw-deliver-orchestration -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/nWave-ai/nWave.git skills-src && mkdir -p .github/skills && cp -r skills-src/nWave/skills/nw-deliver-orchestration .github/skills/nw-deliver-orchestration && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "nw-deliver-orchestration" agent skill from https://github.com/nWave-ai/nWave/tree/main/nWave/skills/nw-deliver-orchestration into .github/skills/nw-deliver-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nw-deliver-orchestration", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nWave-ai/nWave --skill nw-deliver-orchestration -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install nWave-ai/nWave nw-deliver-orchestration --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nWave-ai/nWave.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/nWave/skills/nw-deliver-orchestration .opencode/skills/nw-deliver-orchestration && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "nw-deliver-orchestration" agent skill from https://github.com/nWave-ai/nWave/tree/main/nWave/skills/nw-deliver-orchestration into .opencode/skills/nw-deliver-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nw-deliver-orchestration", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
nw-deliver-orchestration- GitHub stars
- 616
- Token cost
- ~974 tokens
- SKILL.md length
- 351 words
- Files
- 1
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- MIT
At a glance
DELIVER wave orchestration workflow -- 9 phases from baseline to finalization.
- Works in 6 steps: 2: Baseline Creation + Review → 4: Roadmap Creation + Dual Review → 6: Split + Review Each Step → …
- Invokes deliver command
- SKILL.md covers Orchestration Role, 9 Phases, Smart Skip Logic and Quality Gates, plus 5 more sections
- Calls git
What it does
Nw Deliver Orchestration is an agent skill from nWave-ai/nWave. 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.
Its SKILL.md is about 970 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering Quality gates. The repository describes itself as: AI agents that guide you from idea to working code, with you in control at every step. The licence is MIT.
When your agent uses it
- Invokes deliver command
- Tasks that involve Quality gates
Example prompts
- “/nw-deliver-orchestration”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit da401a8. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Nw Deliver Orchestration loads about 974 tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 351 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from nWave-ai/nWave at commit da401a8, republished under its MIT licence (© nWave-ai). 351 words, ~974 tokens.
Download SKILL.mdSave it as
.claude/skills/nw-deliver-orchestration/SKILL.md (or your agent's skills folder).- name
- nw-deliver-orchestration
- description
- 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.
- user-invocable
- false
- disable-model-invocation
- true
DELIVER Wave Orchestration
When invoked via *deliver "{feature-description}", Apex orchestrates the complete DELIVER wave lifecycle.
Orchestration Role
Parse feature description, derive feature ID, execute 9 phases in order. Track state for resume capability.
Invocation: *deliver "Implement user authentication with JWT tokens"
9 Phases
Phase 1-2: Baseline Creation + Review
Create: docs/feature/{feature-id}/deliver/baseline.yaml. Reviewer: @nw-software-crafter-reviewer.
Smart skip: yes (if file exists AND validation.status == "approved").
Phase 3-4: Roadmap Creation + Dual Review
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).
Phase 5-6: Split + Review Each Step
Define steps in: docs/feature/{feature-id}/deliver/roadmap.json. Reviewer: @nw-software-crafter-reviewer (per roadmap step).
Smart skip: yes (if all approved).
Phase 7: Execute All Steps
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.
Phase 8: Finalize
Archive to: docs/evolution/{timestamp}_{feature-id}.md. Clean up workflow files.
Phase 9: Report Completion
Display comprehensive statistics | List all quality gates passed | Show next steps (review evolution doc, push commits, proceed to DEVOPS wave validation).
Smart Skip Logic
- File exists AND
validation.status == "approved"-> skip creation, load for context - File exists but not approved -> skip creation, proceed directly to review
- File missing -> create new artifact
Show full SKILL.md (141 more words)Show less
Quality Gates
| Gate | Reviews | Reviewer |
|---|---|---|
| Baseline | 1 | nw-software-crafter-reviewer |
| Roadmap | 2 | nw-product-owner-reviewer + nw-software-crafter-reviewer |
| Step files | N (per step) | nw-software-crafter-reviewer |
| TDD phases | 2N (per step) | REVIEW + POST-REFACTOR REVIEW |
Total reviews per feature: 3 + 3N (where N = number of steps)
Retry Logic
- Max 2 attempts per review
- Rejected: regenerate artifact with feedback, retry review
- Rejected after 2 attempts: stop workflow, require manual intervention
Stop-on-Failure Policy
- Any review fails after 2 attempts -> stop entire workflow
- Any step execution fails -> stop entire workflow
- User fixes issue manually, re-runs
*deliver(resumes from failure point)
State Tracking
Progress tracked in docs/feature/{feature-id}/deliver/.deliver-progress.json:
{
"project_id": "user-authentication",
"started_at": "2025-01-13T10:30:00",
"last_updated": "2025-01-13T12:45:00",
"completed_phases": ["Phase 1", "Phase 2"],
"current_phase": "Phase 3",
"failed_phase": null,
"failure_reason": null,
"completed_steps": ["01-01", "01-02"],
"failed_step": null,
"skip_flags": {
"baseline": true,
"roadmap": false,
"split": false
},
"orchestration_complete": false
}Resume Capability
On re-invocation: Load .deliver-progress.json -> Skip completed phases -> Resume from failure point or current phase.
Post-Completion
After DELIVER wave completes: All code committed locally (one commit per step) | Evolution document in docs/evolution/ | User reviews commits and evolution document | User pushes: git push | Validate production readiness: *validate-completion.
© nWave-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in nWave/skills/nw-deliver-orchestration of nWave-ai/nWave.
Open the folder on GitHubat commit da401a8
Compare with similar skills
Nw Deliver Orchestration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Nw Deliver Orchestration this skillnWave-ai/nWave | 616 | — | ~974 | Automated safety check: Pass | MIT | |
| Feature Plannerserendipity1004/cc-feature-implementer | 176 | — | ~2.4k | Automated safety check: Pass | None | |
| Ccg Workflowfengshao1227/ccg-workflow | 5.9k | — | ~2.3k | Automated safety check: Pass | MIT | |
| Conducty Checkpointrobertbarclayy/conducty | 176 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Mission Plannerjdforsythe/forge | 151 | — | ~3.5k | Automated safety check: Pass | MIT | |
| Quality Gate0xNyk/lacp | 305 | — | ~382 | Automated safety check: Pass | MIT |
Similar skills
Ccg Workflow
fengshao1227/ccg-workflow
How to run a non-trivial change end to end with the CCG role tools (ccganalyze / ccgdesign / ccgbuild / ccgdebug / ccgoptimize / ccgreview / ccgtest) and the verify- quality gates.
Conducty Checkpoint
robertbarclayy/conducty
Quality gate between parallelization groups. An agent skill from robertbarclayy/conducty.
Mission Planner
jdforsythe/forge
Decomposes goals into team blueprints using evidence-based scaling laws, topology selection, and role design.
Quality Gate
0xNyk/lacp
Production quality gate for agent sessions. An agent skill from 0xNyk/lacp.
Deploy Workflow
nwiizo/ccswarm
Release deployment process for ccswarm. An agent skill from nwiizo/ccswarm.
More from nWave-ai/nWave
All 14 skills in this repoNw Diagram
nWave-ai/nWave
Generates C4 architecture diagrams (context, container, component) in Mermaid or PlantUML.
Nw Diverge
nWave-ai/nWave
Generates 3-5 divergent design directions through JTBD analysis, competitive research, structured brainstorming, and taste evaluation before convergence.
Nw Document
nWave-ai/nWave
Creates evidence-based documentation following DIVIO/Diataxis principles.
Nw Execute
nWave-ai/nWave
A skill your agent uses when a DELIVER roadmap already exists and you need to dispatch exactly one identified step through its TDD cycle.
Nw Forge
nWave-ai/nWave
Creates new specialized agents using the 5-phase workflow (ANALYZE DESIGN CREATE VALIDATE REFINE).
Nw Refactor
nWave-ai/nWave
Applies the Refactoring Priority Premise (RPP) levels L1-L6 for systematic code refactoring.
Related
Categories
Questions about Nw Deliver Orchestration
What does Nw Deliver Orchestration do?
DELIVER wave orchestration workflow -- 9 phases from baseline to finalization. Nw Deliver Orchestration is an agent skill from nWave-ai/nWave. DELIVER wave orchestration workflow -- 9 phases from baseline to finalization.
When should I use Nw Deliver Orchestration?
Nw Deliver Orchestration fits situations like: invokes deliver command; tasks that involve Quality gates.
How do I install Nw Deliver Orchestration in Claude Code?
Run `npx skills add nWave-ai/nWave --skill nw-deliver-orchestration -a claude-code`. Or copy the skill folder (nWave/skills/nw-deliver-orchestration in nWave-ai/nWave) into .claude/skills/nw-deliver-orchestration in your project. Claude Code loads it when a task matches its description.
How do I install Nw Deliver Orchestration in Codex?
Run `npx skills add nWave-ai/nWave --skill nw-deliver-orchestration -a codex`. Or copy the skill folder (nWave/skills/nw-deliver-orchestration in nWave-ai/nWave) into .agents/skills/nw-deliver-orchestration in your project. Codex loads it when a task matches its description.
Can I use Nw Deliver Orchestration in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nWave-ai/nWave --skill nw-deliver-orchestration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nw-deliver-orchestration, .gemini/skills/nw-deliver-orchestration, .github/skills/nw-deliver-orchestration and .opencode/skills/nw-deliver-orchestration in your project.
What does Nw Deliver Orchestration need to run?
Going by SKILL.md and its folder, Nw Deliver Orchestration needs the command-line tools its instructions call (git).
Does Nw Deliver Orchestration access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Nw Deliver Orchestration safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Nw Deliver Orchestration use?
Nw Deliver Orchestration is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Nw Deliver Orchestration use?
About 974 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Nw Deliver Orchestration?
Skills that share tags, products or a category with Nw Deliver Orchestration: Feature Planner (serendipity1004/cc-feature-implementer, 176 stars), Ccg Workflow (fengshao1227/ccg-workflow, 5.9k stars), Conducty Checkpoint (robertbarclayy/conducty, 176 stars) and Mission Planner (jdforsythe/forge, 151 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Nw Deliver Orchestration?
nWave-ai (a GitHub organization) maintains it in nWave-ai/nWave, which has 616 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on September 16, 2026.
Source: nWave-ai/nWave on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.