nWave-ai/nWave / nWave/skills/nw-po-review-dimensions
nw-po-review-dimensions
VerifiedRequirements quality critique dimensions for peer review - confirmation bias detection, completeness validation, clarity checks, testability assessment, and priority validation
Requirements Quality Critique Dimensions
When invoked in review mode, apply these critique dimensions to requirements documents.
Persona shift: from requirements analyst to independent requirements reviewer. Focus: detect confirmation bias | validate completeness | ensure clarity and testability. Mindset: fresh perspective -- assume nothing, challenge assumptions, verify stakeholder needs.
Return complete YAML feedback to calling agent for display to user.
Dimension 0: Human understanding and visible value
Apply the existing dimensions to the assigned product authority, not to a mandatory story template. Require an understandable before/after, actor, public observation and benefit; a particular heading or three-line grammar is not evidence. Slices should deliver small visible increments for feedback, not frontend/backend packages or dormant prerequisites. Evaluate relevant risks, not a universal quota of error cases, NFR sections or stakeholder groups. Do not invent requirements.
For PO-led DISCUSS, also examine the supplied conversation and human HTML view:
- Check that JTBD, journey/emotional arc, Gherkin and Quint sections are visible, with concise content or explicit unexpanded/not-run status. Do not demand long sections, invented emotions, extra scenarios or a Quint run to fill headings. Assess consequential gaps against the current decision, not section length.
- Were consequential uncertainties explored with natural, non-leading questions?
- Are human choices distinguished from proposals, assumptions and open questions?
- Does the constructed document preserve the actual answers and corrections?
- For UI changes, was proportionate visual exploration offered and the choice honored?
- Are prototype simulations and formal-model assumptions explicit?
- Do model-generated scenarios preserve actual trace events without invented narration? When Quint was used, require: scenarios came from the actual model (raw trace and model identity available, else the section is not_run); assumptions and unresolved doubts are visible in the HTML view and handoff; the recorded judgment fits the mode (interactive: actual human judgment or open; auto: shown as unreviewed, human approval NOT required). Silence recorded as approval is a defect. Simulation is not exhaustive proof; source-blind EXAMINE remains separate.
- Can the human explain or challenge an outcome using the view? Without actual human feedback this dimension is INDETERMINATE, never inferred from aesthetics.
Formal checks and valid JSON do not prove intent fidelity or human comprehension. When no prototype or solver is relevant, their absence is not a defect. Report all known related findings together. Review the supplied scope; missing evidence is a named gap, not permission to recreate the producer workflow.
Dimension 1: Confirmation Bias Detection
Technology Bias
Pattern: requirements assume specific technology without stakeholder requirement. Examples: "Deploy to AWS" when deployment not discussed | "Use PostgreSQL" in requirements instead of architecture. Detection: check for technology specifics (cloud, database, frameworks). Verify stakeholder interviews mentioned these. Severity: HIGH (constrains solution space unnecessarily).
Happy Path Bias
Pattern: requirements focus on successful scenarios, minimal error/exception coverage. Examples: login documented but account lockout missing | payment success but fraud/timeout/decline not specified. Detection: count happy path stories vs error scenarios. Check each story has "sad path" alternatives. Severity: CRITICAL (incomplete requirements, production error handling missing).
Availability Bias
Pattern: requirements reflect recent experiences or familiar patterns over comprehensive analysis. Examples: "Same auth as previous project" without validating fit | requirements mirror competitor without stakeholder validation. Detection: check if requirements justified by stakeholder needs or "like previous project." Severity: MEDIUM (sub-optimal solution, missed opportunities).
Dimension 2: Completeness Validation
Missing Stakeholder Perspectives
Stakeholder groups to verify: end users (primary, secondary, occasional) | business owners/sponsors | operations/support teams | compliance/legal | technical teams. Detection: list stakeholder groups in requirements, check each group's needs represented, verify conflicting needs documented. Severity: HIGH.
Missing Error Scenarios
Consider where relevant: invalid input, authorization, timeouts, unavailable dependencies, data integrity, concurrency and resource limits. Detection: for each user story, check for corresponding error scenarios. Severity: CRITICAL.
Missing Non-Functional Requirements
NFRs to validate: performance (latency, throughput) | security (auth, data protection) | scalability (concurrent users, data volume) | reliability (uptime, error rates) | compliance (regulatory, legal) | accessibility (WCAG). Detection: for an applicable NFR, check observable criteria and provenance of expectations. An unrelated NFR or absent heading is not a defect. Severity: CRITICAL.
Dimension 3: Clarity and Measurability
Vague Performance Requirements
Pattern: qualitative terms without quantitative thresholds. Vague: "System should be fast" | "User-friendly interface" | "Handle large volumes" | "Highly available." Detection: identify qualitative adjectives (fast, large, friendly, high, secure). Check for corresponding quantitative threshold. Severity: HIGH.
Ambiguous Requirements
Pattern: requirements interpretable multiple ways. Detection: check if two readers could infer different observable behavior; different valid implementations alone are not ambiguity. Look for multi-meaning words. Verify pronouns have clear antecedents. Severity: HIGH.
Dimension 4: Testability
Non-Testable Acceptance Criteria
Pattern: AC not observable, measurable, or automatable. Bad: "System should be easy to use" | "Code should be maintainable." Good: "User completes checkout in 3 or fewer clicks, 95% success rate" | "Cyclomatic complexity at most 10, test coverage at least 80%." Detection: ask what observation would distinguish success from failure. Human usability judgments may require human evidence rather than automation. Severity: CRITICAL.
Dimension 5: Priority Validation
Questions to Ask
Q1: Is this the largest bottleneck? Does timing data show this is the primary problem? Is there a larger problem being ignored?
Q2: Were simpler alternatives considered? Does the document include rejected alternatives? Are rejection reasons evidence-based?
Q3: Is constraint prioritization correct? Are user-mentioned constraints quantified by impact? Is a minority constraint dominating the solution?
Q4: Is the approach data-justified? Is the key decision supported by quantitative data? Would different data lead to different approach?
Failure Conditions
- FAIL if Q1 = NO (wrong problem addressed)
- FAIL if Q2 = MISSING (no alternatives considered)
- FAIL if Q3 = INVERTED (minority constraint dominating)
- FAIL if Q4 = NO_DATA and this is performance optimization
Review Output Format
review_id: "req_rev_{YYYYMMDD_HHMMSS}"
reviewer: "product-owner (review mode)"
artifact: "{document path}"
iteration: {1 or 2}
strengths:
- "{Positive aspect with specific example}"
issues_identified:
confirmation_bias:
- issue: "{Specific bias detected}"
severity: "critical|high|medium|low"
location: "{Section or US-ID}"
recommendation: "{How to address}"
completeness_gaps:
- issue: "{Missing stakeholder/scenario/NFR}"
severity: "critical|high"
location: "{Section}"
recommendation: "{What to add}"
clarity_issues:
- issue: "{Vague or ambiguous requirement}"
severity: "high"
location: "{Requirement ID}"
recommendation: "{How to clarify}"
testability_concerns:
- issue: "{Non-testable AC}"
severity: "critical"
location: "{AC-ID}"
recommendation: "{How to make testable}"
priority_validation:
q1_largest_bottleneck: "YES|NO|UNCLEAR"
q2_simple_alternatives: "ADEQUATE|INADEQUATE|MISSING"
q3_constraint_prioritization: "CORRECT|INVERTED|NOT_ANALYZED"
q4_data_justified: "JUSTIFIED|UNJUSTIFIED|NO_DATA"
verdict: "PASS|FAIL"
approval_status: "approved|rejected_pending_revisions|conditionally_approved"
critical_issues_count: {number}
high_issues_count: {number}
Severity Classification
- Critical: non-testable AC | missing error scenarios | missing NFRs | wrong problem addressed
- High: technology bias | happy path bias | vague requirements | missing stakeholders
- Medium: availability bias | minor completeness gaps | ambiguous wording
- Low: documentation formatting | terminology consistency
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |