requirements-clarity-scoring

When gathering requirements during discovery phase to measure answer quality and decide when to proceed.

⭐5stars🔀1forks📁View on GitHub🕐Updated Jan 11, 2026

When & Why to Use This Skill

The Requirements Clarity Scoring skill is a professional framework designed to quantify the quality of information gathered during the project discovery phase. It utilizes a standardized 1-5 scoring system and weighted evaluation across critical dimensions—such as problem definition and success criteria—to provide a data-driven 'Proceed' or 'Stop' signal. This ensures that teams only move forward when requirements are actionable and crystal clear, significantly reducing the risk of scope creep and project failure.

Use Cases

  • Project Discovery & Kickoff: Evaluate stakeholder input during initial meetings to determine if the project scope and objectives are defined well enough to begin technical planning.
  • Risk Assessment: Identify 'vague' or 'unclear' requirements in high-priority areas like technical constraints to prevent costly mid-project pivots.
  • Stakeholder Management: Provide objective, numerical feedback to stakeholders when their requirements lack the necessary detail for implementation, justifying the need for further clarification.
  • Quality Gate Implementation: Use the weighted average score as a formal 'gate' that must be passed before transitioning from the discovery phase to the execution phase.
namerequirements-clarity-scoring
descriptionWhen gathering requirements during discovery phase to measure answer quality and decide when to proceed.
version1.1.0
tokens~350
confidencehigh
- https//www.reqview.com/doc/iso-iec-ieee-29148-templates/
last_validated2025-12-10
next_review2025-12-24
tags[requirements, discovery, clarity, planning]

When to Use

When gathering requirements during discovery phase to measure answer quality and decide when to proceed.

Patterns

Clarity Scoring (1-5)

5 = CRYSTAL CLEAR
    - Specific, measurable answer
    - No ambiguity
    - Actionable immediately
    Example: "Response time must be <200ms at p95"

4 = CLEAR
    - Mostly specific
    - Minor gaps fillable
    Example: "Response should be fast" + "under 500ms is acceptable"

3 = PARTIAL
    - General direction known
    - Needs follow-up questions
    Example: "Performance matters" (how much? which operations?)

2 = VAGUE
    - Conflicting information
    - Multiple interpretations possible
    Example: "It should just work" (what does 'work' mean?)

1 = UNCLEAR
    - No answer or "I don't know"
    - Requires stakeholder escalation
    Example: "We haven't decided yet"

Proceed Threshold

Calculate average score across all answers:

≥ 4.0  → PROCEED to next phase
3.5-4.0 → PROCEED with noted risks
3.0-3.5 → CLARIFY critical gaps first
< 3.0  → STOP - too many unknowns

Question Categories to Score

1. Problem Definition (weight: HIGH)
2. Success Criteria (weight: HIGH)
3. Scope Boundaries (weight: HIGH)
4. Technical Constraints (weight: MEDIUM)
5. Timeline/Budget (weight: MEDIUM)
6. Nice-to-haves (weight: LOW)

Anti-Patterns

  • Proceeding with average < 3.0
  • Ignoring LOW scores on HIGH weight items
  • Assuming unstated requirements
  • Not documenting score justification

Verification Checklist

  • All questions scored 1-5
  • Weighted average calculated
  • HIGH weight items all ≥ 3
  • Gaps documented with follow-up plan