메뉴
Detects current wave progress for a feature and resumes at the next step. Scans docs/feature/ for artifacts.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | nw-continue |
| description | Detects current wave progress for a feature and resumes at the next step. Scans docs/feature/ for artifacts. |
| user-invocable | false |
| argument-hint | [feature-id] - Optional: omit to auto-detect from docs/feature/ |
Wave: CROSS_WAVE (entry point) | Agent: Main Instance (self — wizard) | Command: /nw-continue
Scans docs/feature/ for active projects, detects wave artifacts, displays progress summary, launches next wave command. Eliminates manual artifact inspection when returning after hours/days.
You (main Claude instance) run this wizard directly. No subagent delegation.
If project ID provided as argument, use it directly.
Otherwise scan docs/feature/ for project directories:
ls -d docs/feature/*/
No directories found: Display "No active projects found under docs/feature/." Suggest /nw-new. Stop.
If multiple directories exist, list by most recent file modification:
find docs/feature/{feature-id}/ -type f -printf '%T@ %p\n' | sort -rn | head -1
Present via AskUserQuestion: project name|last modified date|most recent first. Ask user to select.
Check each wave's artifacts using Wave Detection Rules in ~/.claude/nWave/skills/common/wizard-shared-rules.md.
Check before showing progress:
Empty/corrupted artifacts: Verify file size > 0 for each "complete" artifact. If empty, flag: "Warning: user-stories.md exists but is empty (0 bytes). Recommend re-running DISCUSS wave."
Non-adjacent waves (skipped): If artifacts exist for non-consecutive waves (e.g., DISCUSS + DELIVER but no DESIGN/DISTILL), warn with options:
If DELIVER in progress, show step-level detail:
docs/feature/{id}/deliver/execution-log.json — count COMMIT/PASS steps, find first without COMMIT/PASS.develop-progress.json if exists: check last failure pointFeature: {feature-id}
DISCOVER ○ not started
DISCUSS ● complete
DESIGN ● complete
DISTILL ◐ in progress
DELIVER ○ not started
Next: DISTILL — Create acceptance tests
Symbols: ● complete | ◐ in progress | ○ not started
Recommend next wave: resume in-progress wave|successor of last complete wave. Show via AskUserQuestion for confirmation. After confirmation, invoke recommended wave command by reading its task file, passing project ID as argument.
| Error | Response |
|---|---|
No docs/feature/ directory | Suggest /nw-new |
| Empty project directory | Suggest /nw-new or re-run from DISCUSS |
| Corrupted artifact (0 bytes) | Flag file, recommend re-running that wave |
| Skipped waves | Warn, offer gap-fill or continue options |
| Cannot parse execution-log.json | Show raw file status, suggest manual review |
docs/feature//nw-continue
Wizard finds one project: notification-service. DISCUSS artifacts exist (complete), no DESIGN artifacts. Shows progress, recommends DESIGN. User confirms, wizard launches /nw-design notification-service.
/nw-continue rate-limiting
Wizard checks rate-limiting project. All waves through DISTILL complete, DELIVER in progress (steps 01-01 through 02-01 done). Shows "Next: step 02-02", launches /nw-deliver "rate-limiting".
/nw-continue
Wizard finds rate-limiting (modified today) and user-notifications (modified 3 days ago). Lists them, user picks rate-limiting. Wizard shows progress and recommends next wave.
/nw-continue
Wizard finds no docs/feature/ directories. Shows "No active projects found" and suggests /nw-new.
Cross-agent collaboration protocols, workflow handoff patterns, and commit message formats for TDD/Mikado/refactoring workflows
Orchestrates the full DELIVER wave end-to-end (roadmap > execute-all > finalize). Use when all prior waves are complete and the feature is ready for implementation.
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.
Creates a phased roadmap.json for a feature goal with acceptance criteria and TDD steps. Use when planning implementation steps before execution.
Dispatches one unit of DELIVER work to a specialized agent for TDD execution. Runs a single roadmap.json step through the TDD cycle.
Deep knowledge for Outside-In TDD - double-loop architecture, ATDD integration, port-to-port testing, walking skeletons, and test doubles policy