nWave/skills/nw-fast-forward/SKILL.md
Fast-forwards through remaining waves end-to-end without stopping for review between waves.
npx skillsauth add nwave-ai/nwave nw-fast-forwardInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Wave: CROSS_WAVE (entry point) | Agent: Main Instance (self — orchestrator) | Command: /nw-fast-forward
Chains remaining waves end-to-end after single user confirmation. Detects current progress (like /nw-continue), shows planned sequence, runs each wave automatically — DISCUSS > DESIGN > DEVOPS > DISTILL > DELIVER — without stopping between waves.
You (main Claude instance) run this orchestration directly. Each wave invoked by reading its task file.
DISCOVER skipped by default — requires interactive customer interview data that cannot be auto-generated. Use --from=discover to include.
Accept: feature description (new project)|--from flag with optional feature ID|no arguments (auto-detect from docs/feature/)
New project (description provided): Derive feature ID per ~/.claude/nWave/skills/common/wizard-shared-rules.md (Feature ID Derivation). Show derived ID, allow override via AskUserQuestion. Create docs/feature/{feature-id}/.
Existing project (no description): Scan docs/feature/ (same as /nw-continue Step 1-2). If multiple, ask user to select.
Check wave artifacts using Wave Detection Rules in ~/.claude/nWave/skills/common/wizard-shared-rules.md.
Default order (DISCOVER skipped): DISCUSS > DESIGN > DEVOPS > DISTILL > DELIVER
With --from flag: Validate prerequisite artifacts exist. If missing: "Cannot start from {wave} — {missing} artifacts missing. Run /nw-continue to fill the gap." Start from specified wave.
Without --from: Find first incomplete wave, start from there.
Feature: {feature-id}
Fast-forward plan:
1. DISCUSS — Define requirements and user stories
2. DESIGN — Architecture and technology selection
3. DEVOPS — Platform and infrastructure readiness
4. DISTILL — Acceptance tests (Given-When-Then)
5. DELIVER — TDD implementation
This will run all 5 waves without stopping for review.
If some waves complete, show as skipped:
Fast-forward plan:
✓ DISCUSS — complete
✓ DESIGN — complete
1. DEVOPS — Platform and infrastructure readiness
2. DISTILL — Acceptance tests (Given-When-Then)
3. DELIVER — TDD implementation
3 waves will execute without stopping.
One-time confirmation via AskUserQuestion.
For each wave:
nWave/tasks/nw/{wave}.md)Between waves show brief status:
✓ DISCUSS complete — user-stories.md, story-map.md created
Starting DESIGN...
If any wave fails:
✗ {WAVE} failed
Error: [details]
Progress saved. Run /nw-continue to resume from {WAVE}.
/nw-continue for manual resume✓ Fast-forward complete for {feature-id}
DISCUSS ● complete
DESIGN ● complete
DEVOPS ● complete
DISTILL ● complete
DELIVER ● complete
All acceptance tests pass. Feature is ready.
| Error | Response |
|-------|----------|
| No description and no existing projects | Suggest /nw-new |
| --from with missing prerequisites | List missing artifacts, refuse |
| Wave failure mid-pipeline | Stop, show error, suggest /nw-continue |
| Artifact verification fails after wave | Treat as wave failure |
| Name conflict on new project | Same as /nw-new conflict handling |
/nw-continue suggestion/nw-fast-forward "Upgrade authentication to OAuth2"
Wizard derives oauth2-upgrade, detects no prior artifacts, shows plan: DISCUSS > DESIGN > DEVOPS > DISTILL > DELIVER. User confirms. All 5 waves execute in sequence.
/nw-fast-forward
Wizard finds notification-service with DISCUSS complete. Shows plan: DESIGN > DEVOPS > DISTILL > DELIVER. User confirms. 4 waves execute.
/nw-fast-forward --from=distill rate-limiting
Wizard validates DESIGN artifacts exist for rate-limiting. Shows plan: DISTILL > DELIVER. User confirms. 2 waves execute.
/nw-fast-forward "Add payment processing"
DISCUSS succeeds, DESIGN succeeds, DEVOPS fails. Pipeline stops. Shows error and suggests /nw-continue to resume from DEVOPS.
testing
Acceptance test creation methodology for the DISTILL wave. Domain knowledge for the acceptance designer agent: port-to-port principle, prior wave reading, wave-decision reconciliation, graceful degradation, and document back-propagation.
development
Cross-agent collaboration protocols, workflow handoff patterns, and commit message formats for TDD/Mikado/refactoring workflows
development
Creates a phased roadmap.json for a feature goal with acceptance criteria and TDD steps. Use when planning implementation steps before execution.
testing
Acceptance test creation methodology for the DISTILL wave. Domain knowledge for the acceptance designer agent: port-to-port principle, prior wave reading, wave-decision reconciliation, graceful degradation, and document back-propagation.