/nw-review-workflow
Detailed review process, v2 validation checklist, and scoring methodology for agent definition reviews
$ npx -y skills add nWave-ai/nWave --skill nw-review-workflow --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/nw-review-workflow
Context preview
The summary Claude sees to decide when to auto-load this skill.
Detailed review process, v2 validation checklist, and scoring methodology for agent definition reviews
SKILL.md
nw-review-workflow.SKILL.mdname: nw-review-workflow
description: Detailed review process, v2 validation checklist, and scoring methodology for agent definition reviews
user-invocable: false
disable-model-invocation: true
Agent Review Workflow
V2 Validation Checklist (11 Points)
Run against every agent under review. Each item pass/fail.
1. **Frontmatter format**: `---` delimited YAML with `name` and `description` 2. **Size compliance**: Under 400 lines; domain knowledge in Skills 3. **Divergence-only**: Only behaviors diverging from Claude defaults 4. **Calm language**: No "CRITICAL", "MANDATORY", "ABSOLUTE" 5. **Examples present**: 3-5 canonical for critical/subtle behaviors 6. **Least privilege tools**: Minimum needed in frontmatter 7. **maxTurns set**: Present in frontmatter 8. **Platform safety**: Via frontmatter/hooks, not prose 9. **Affirmative phrasing**: "Do X" not "Don't do Y" 10. **Consistent terminology**: One term per concept 11. **Clear delegation**: Description states when to delegate
Scoring Methodology
Per-Dimension Scoring
For each of 7 critique dimensions (from critique-dimensions skill):
- **Pass**: All checks satisfied
- **Fail**: One or more checks not satisfied
Verdict Logic
IF any high-severity dimension fails:
verdict = "revisions_needed"
ELIF count(medium-severity failures) >= 3:
verdict = "revisions_needed"
ELSE:
verdict = "approved"
High-severity: template_compliance, size_and_focus, safety_implementation, priority_validation Medium-severity: divergence_quality, language_and_tone, examples_quality
Evidence Requirements
Every finding includes: **Dimension** (which of 7) | **Severity** (high/medium/low) | **Finding** (observed, with line numbers/counts) | **Recommendation** (specific fix action)
Common V1 to V2 Migration Issues
| Residual Pattern | What to Flag | |-----------------|-------------| | Embedded YAML config blocks | Should be frontmatter or removed | | `activation-instructions` section | Remove -- Claude Code handles activation | | `IDE-FILE-RESOLUTION` section | Remove -- not needed in v2 | | `commands` with 10+ entries | Reduce to 3-5 focused | | Inline `embed_knowledge` | Extract to Skills | | 5+ "production frameworks" | Remove -- platform handles safety | | `CRITICAL:` prefixed instructions | Rephrase as calm direct statements | | Python/YAML safety code examples | Remove -- aspirational, not executable |
Peer Review Protocol
1. Receive agent file path from builder 2. Execute full dimension review 3. Return structured YAML verdict 4. If `revisions_needed`, include prioritized fix list 5. Builder revises and resubmits (max 2 iterations) 6. On second rejection, escalate to user
Command Template Review
Additional checks for nWave command files (tasks):
- Size: 50-60 lines target; >60 warning, >150 major, >500 blocker
- Structure: agent activation metadata, context files section, success criteria
- Delegation: business logic belongs in agent, not command
- No embedded procedural steps (STEP 1, STEP 2)
Read more
name: nw-review-workflow description: Detailed review process, v2 validation checklist, and scoring methodology for agent definition reviews user-invocable: false disable-model-invocation: true
Agent Review Workflow
V2 Validation Checklist (11 Points)
Run against every agent under review. Each item pass/fail.
1. **Frontmatter format**: `---` delimited YAML with `name` and `description` 2. **Size compliance**: Under 400 lines; domain knowledge in Skills 3. **Divergence-only**: Only behaviors diverging from Claude defaults 4. **Calm language**: No "CRITICAL", "MANDATORY", "ABSOLUTE" 5. **Examples present**: 3-5 canonical for critical/subtle behaviors 6. **Least privilege tools**: Minimum needed in frontmatter 7. **maxTurns set**: Present in frontmatter 8. **Platform safety**: Via frontmatter/hooks, not prose 9. **Affirmative phrasing**: "Do X" not "Don't do Y" 10. **Consistent terminology**: One term per concept 11. **Clear delegation**: Description states when to delegate
Scoring Methodology
Per-Dimension Scoring
For each of 7 critique dimensions (from critique-dimensions skill):
- **Pass**: All checks satisfied
- **Fail**: One or more checks not satisfied
Verdict Logic
IF any high-severity dimension fails: verdict = "revisions_needed" ELIF count(medium-severity failures) >= 3: verdict = "revisions_needed" ELSE: verdict = "approved"
High-severity: template_compliance, size_and_focus, safety_implementation, priority_validation Medium-severity: divergence_quality, language_and_tone, examples_quality
Evidence Requirements
Every finding includes: **Dimension** (which of 7) | **Severity** (high/medium/low) | **Finding** (observed, with line numbers/counts) | **Recommendation** (specific fix action)
Common V1 to V2 Migration Issues
| Residual Pattern | What to Flag | |-----------------|-------------| | Embedded YAML config blocks | Should be frontmatter or removed | | `activation-instructions` section | Remove -- Claude Code handles activation | | `IDE-FILE-RESOLUTION` section | Remove -- not needed in v2 | | `commands` with 10+ entries | Reduce to 3-5 focused | | Inline `embed_knowledge` | Extract to Skills | | 5+ "production frameworks" | Remove -- platform handles safety | | `CRITICAL:` prefixed instructions | Rephrase as calm direct statements | | Python/YAML safety code examples | Remove -- aspirational, not executable |
Peer Review Protocol
1. Receive agent file path from builder 2. Execute full dimension review 3. Return structured YAML verdict 4. If `revisions_needed`, include prioritized fix list 5. Builder revises and resubmits (max 2 iterations) 6. On second rejection, escalate to user
Command Template Review
Additional checks for nWave command files (tasks):
- Size: 50-60 lines target; >60 warning, >150 major, >500 blocker
- Structure: agent activation metadata, context files section, success criteria
- Delegation: business logic belongs in agent, not command
- No embedded procedural steps (STEP 1, STEP 2)
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
Other skills on nwave.
- /nw-ab-critique-dimensions
Review dimensions for validating agent quality - template compliance, safety, testing, and priority validation
Open skill - /nw-abr-critique-dimensions
Review dimensions for validating agent quality - template compliance, safety, testing, and priority validation
Open skill - /nw-ad-critique-dimensions
Review dimensions for acceptance test quality - happy path bias, GWT compliance, business language purity, coverage completeness, walking skeleton user-centricity, priority validation, observable behavior assertions, traceability coverage, and walking skeleton boundary proof
Open skill - /nw-agent-creation-workflow
Detailed 5-phase workflow for creating agents - from requirements analysis through validation and iterative refinement
Open skill - /nw-agent-testing
5-layer testing approach for agent validation including adversarial testing, security validation, and prompt injection resistance
Open skill - /nw-architectural-styles-tradeoffs
Architectural style selection decision matrices, trade-off analysis, structural enforcement rules, and combination patterns. Load when choosing or evaluating architecture styles.
Open skill

