Stats
Actions
Tags
From nw
Provides DevOps review criteria for phase handoffs, deployment readiness, traceability, priority validation, and functional integration checks.
How this skill is triggered — by the user, by Claude, or both
Slash command
/nw:nw-par-review-criteriaThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Pattern**: Phase handoffs missing required artifacts or approvals.
Pattern: Phase handoffs missing required artifacts or approvals.
Required per Phase:
Severity: critical. Verify all artifacts present and peer-reviewed before phase transition.
Pattern: Feature marked "ready" but missing production prerequisites.
Required: All tests passing (100%) | Production configuration complete | Monitoring/alerting configured | Runbook/operational docs created | Rollback plan documented.
Severity: critical. Complete missing prerequisite before marking deployment-ready.
Pattern: Cannot trace production code back to requirements.
Required: User stories map to acceptance tests | Acceptance tests map to production code | Code changes traceable to commits | All AC verified in production.
Severity: high. Establish traceability chain: user-story -> acceptance-tests -> code-commits.
Purpose: Validate roadmap addresses largest bottleneck first, not secondary concern.
Q1: Is this the largest bottleneck? Does timing data show primary problem? Larger problem being ignored? Assessment: YES / NO / UNCLEAR.
Q2: Were simpler alternatives considered? Roadmap includes rejected alternatives? Rejection reasons evidence-based? Simpler solution achieves 80% benefit? Assessment: ADEQUATE / INADEQUATE / MISSING.
Q3: Is constraint prioritization correct? Constraints quantified by impact? Architecture addresses constraint-free opportunities first? Minority constraint dominating? (flag if >50% of solution for <30% of problem). Assessment: CORRECT / INVERTED / NOT_ANALYZED.
Q4: Is architecture data-justified? Key architectural decision supported by quantitative data? Different data leads to different architecture? Assessment: JUSTIFIED / UNJUSTIFIED / NO_DATA.
Purpose: Verify feature wired into system entry point -- prevents Testing Theatre. A feature with 100% test coverage but 0% wiring tests is not complete.
Validation Criteria:
Gate failure response: Block finalization | report specific integration gap with evidence | require integration step before completion.
npx claudepluginhub nwave-ai/nwave --plugin nwFinal validation gate before deploy: checks pipeline execution, code quality, security, QA, documentation, and generates approval/rejection report. Activates on deploy readiness or re-review.
Provides structured critique dimensions for peer reviewing code and tests: detects implementation bias (YAGNI, premature optimization), validates test quality (coupling, flakiness), checks completeness and priorities.
Performs comprehensive quality audits verifying planning conformance, DDD validation, security checks, tests, browser verification, and metrics before deployment or PR merge.