nw-ab-critique-dimensi…
Review dimensions for validating agent quality - template compliance, safety, testing, and priority validation
Detects current wave progress for a feature and resumes at the next step. Scans docs/feature/ for artifacts.
$ npx -y skills add nWave-ai/nWave --skill nw-continue --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/nw-continueContext preview
The summary Claude sees to decide when to auto-load this skill.
Detects current wave progress for a feature and resumes at the next step. Scans docs/feature/ for artifacts.
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 -1Present 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: 1. Fill the gap — start from missing wave 2. Continue as-is 3. Show all artifacts for manual review
If DELIVER in progress, show step-level detail:
Feature: {feature-id}
DISCOVER ○ not started
DISCUSS ● complete
DESIGN ● complete
DISTILL ◐ in progress
DELIVER ○ not started
Next: DISTILL — Create acceptance testsSymbols: ● 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 |
/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`.
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).
Repo: nWave-ai/nWave
Review dimensions for validating agent quality - template compliance, safety, testing, and priority validation
Review dimensions for validating agent quality - template compliance, safety, testing, and priority validation
Review dimensions for acceptance test quality - happy path bias, GWT compliance, business language purity, coverage completeness, walking skeleton…
Detailed 5-phase workflow for creating agents - from requirements analysis through validation and iterative refinement
5-layer testing approach for agent validation including adversarial testing, security validation, and prompt injection resistance
Architectural style selection decision matrices, trade-off analysis, structural enforcement rules, and combination patterns. Load when choosing or evaluating…