OpenParable
Skip to content
← Back to skills

Requirements Clarity Scoring

Productivity
requirements-clarity-scoring

Requirements Clarity Scoring is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/data/requirements-clarity-scoring/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/requirements-clarity-scoring, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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