nw-ab-critique-dimensi…
Review dimensions for validating agent quality - template compliance, safety, testing, and priority validation
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.
$ npx -y skills add nWave-ai/nWave --skill nw-deliver-orchestration --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/nw-deliver-orchestrationContext preview
The summary Claude sees to decide when to auto-load this skill.
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.
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
When invoked via `*deliver "{feature-description}"`, Apex orchestrates the complete DELIVER wave lifecycle.
Parse feature description, derive feature ID, execute 9 phases in order. Track state for resume capability.
**Invocation**: `*deliver "Implement user authentication with JWT tokens"`
Create: `docs/feature/{feature-id}/deliver/baseline.yaml`. Reviewer: @nw-software-crafter-reviewer. Smart skip: yes (if file exists AND `validation.status == "approved"`).
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).
Define steps in: `docs/feature/{feature-id}/deliver/roadmap.json`. Reviewer: @nw-software-crafter-reviewer (per roadmap step). Smart skip: yes (if all approved).
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.
Archive to: `docs/evolution/{timestamp}_{feature-id}.md`. Clean up workflow files.
Display comprehensive statistics | List all quality gates passed | Show next steps (review evolution doc, push commits, proceed to DEVOPS wave validation).
| 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)
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
}On re-invocation: Load `.deliver-progress.json` -> Skip completed phases -> Resume from failure point or current phase.
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`.
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…