/nw-spike
Runs a timeboxed PROBE to validate one core assumption, then optionally PROMOTES the probe into a walking skeleton — the first e2e thin slice of the feature, committed and demo-able. Use after DISCUSS when the feature involves a new mechanism, performance requirement, or
Claude Code
$ npx -y skills add nWave-ai/nWave --skill nw-spike --agent claude-code
Codex
$ npx skills add nWave-ai/nWave --skill nw-spike -a codex -y
Cursor
$ npx skills add nWave-ai/nWave --skill nw-spike -a cursor -y
Gemini CLI
$ npx skills add nWave-ai/nWave --skill nw-spike -a gemini-cli -y
GitHub Copilot
$ npx skills add nWave-ai/nWave --skill nw-spike -a github-copilot -y
OpenCode
$ npx skills add nWave-ai/nWave --skill nw-spike -a opencode -y
Windsurf
$ npx skills add nWave-ai/nWave --skill nw-spike -a windsurf -y
SKILL.md
nw-spike.SKILL.mdname: nw-spike
description: A bounded probe of one product, visual-experience or technical uncertainty; returns evidence to its owner without starting a wave or promoting code automatically.
user-invocable: true
argument-hint: '[question or uncertain experience]'
NW-SPIKE
The LLM selects a probe when an unanswered question changes a product or design decision. This is a technique inside DISCUSS/DESIGN, not an extra mandatory wave. Honor an existing delegation or stop boundary; do not repeat permission requests.
1. State one question, the evidence that would change the decision, and a bounded scope/time budget. Skip a probe that cannot inform a decision. 2. Reuse relevant artifacts. For visual uncertainty, the PO supplies actor, journey and feedback question; `nw-ux-designer` supplies UX/UI competence. Choose sketch, wireframe or navigable prototype according to uncertainty. For technical uncertainty, select the applicable technical specialist. 3. Keep artifacts and findings in the caller-owned persistent workspace, outside production paths; never rely on `/tmp` for valuable work. Use the project's native toolchain. Clearly label simulated data, mocked effects and absent integration. Prototype only enough behavior to answer the question. 4. Observe the result. For a visual prototype, show it to the human and retain actual feedback separately from model inference. Pending feedback stays open; an attractive page is not usability evidence. Do not force a binary verdict for a human preference or an unresolved question. 5. Return evidence, limitations and the decision still needed to the PO or architect, who owns any resulting authority revision. Do not write wave authority or handover documents yourself.
No automatic promotion, commit or cleanup. A separately selected implementation may reuse prototype code after normal design, oracle and review work. A mocked prototype is not the feature's walking skeleton. Preserve useful evidence before any explicitly selected disposal; meaningful prototype changes require renewed feedback, not reuse of an old approval.
Read more
name: nw-spike description: A bounded probe of one product, visual-experience or technical uncertainty; returns evidence to its owner without starting a wave or promoting code automatically. user-invocable: true argument-hint: '[question or uncertain experience]'
NW-SPIKE
The LLM selects a probe when an unanswered question changes a product or design decision. This is a technique inside DISCUSS/DESIGN, not an extra mandatory wave. Honor an existing delegation or stop boundary; do not repeat permission requests.
1. State one question, the evidence that would change the decision, and a bounded scope/time budget. Skip a probe that cannot inform a decision. 2. Reuse relevant artifacts. For visual uncertainty, the PO supplies actor, journey and feedback question; `nw-ux-designer` supplies UX/UI competence. Choose sketch, wireframe or navigable prototype according to uncertainty. For technical uncertainty, select the applicable technical specialist. 3. Keep artifacts and findings in the caller-owned persistent workspace, outside production paths; never rely on `/tmp` for valuable work. Use the project's native toolchain. Clearly label simulated data, mocked effects and absent integration. Prototype only enough behavior to answer the question. 4. Observe the result. For a visual prototype, show it to the human and retain actual feedback separately from model inference. Pending feedback stays open; an attractive page is not usability evidence. Do not force a binary verdict for a human preference or an unresolved question. 5. Return evidence, limitations and the decision still needed to the PO or architect, who owns any resulting authority revision. Do not write wave authority or handover documents yourself.
No automatic promotion, commit or cleanup. A separately selected implementation may reuse prototype code after normal design, oracle and review work. A mocked prototype is not the feature's walking skeleton. Preserve useful evidence before any explicitly selected disposal; meaningful prototype changes require renewed feedback, not reuse of an old approval.
AI agents that guide you from idea to working code, with human judgment at every gate. nWave runs inside Claude Code. It breaks feature delivery into seven waves (discover, diverge, discuss, design, devops, distill, deliver).
Other skills on nwave.
More skills from other plugins.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
ask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Questions about nw-spike.
- Which coding agents can use nw-spike?
- nw-spike installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

