Ambiguity Rubric#
A 5-dimension rubric for quantitatively evaluating ambiguity in spec documents. Final score = weighted average (0.0 = perfectly clear, 1.0 = completely ambiguous)
Pass Criteria#
| Grade | Score Range | Verdict |
|---|---|---|
| CLEAR | 0.0 ~ 0.2 | Pass โ Implementation-ready |
| WARNING | 0.2 ~ 0.3 | Conditional โ Re-evaluate after fixing flagged items |
| AMBIGUOUS | 0.3 ~ 0.5 | Fail โ Major ambiguities must be resolved |
| UNCLEAR | 0.5 ~ 1.0 | Reject โ Spec rewrite required |
Dimension 1: Lexical Precision โ Weight 0.25#
Whether ambiguous words/expressions have been replaced with specific values or definitions.
Prohibited Word List (Ambiguous Expressions)#
Locale-tagged. The lexical scan MUST match the spec's own language. A Korean spec is scanned with the Korean column; do NOT rely on the English column alone (that misses every Korean vague term and silently scores 0.0 โ see the locale rule below).
| English (ambiguous) | Korean (ambiguous) | Clear Replacement Example |
|---|---|---|
| fast, quickly | ๋น ๋ฅด๊ฒ, ์ ์ํ | p95 response under 200ms |
| many, large amount | ๋๋, ๋ค์, ๋ง์ด | 10,000 or more |
| appropriate, properly | ์ ์ ํ, ์๋ง๊ฒ | {specify concrete criteria} |
| simple, easy | ๊ฐ๋จํ, ์ฝ๊ฒ | Complete within 3 steps |
| etc., and so on | ๋ฑ๋ฑ, ๊ธฐํ | Enumerate complete list |
| if needed, depending on | ํ์์, ์ํฉ์ ๋ฐ๋ผ | {specify exact conditions} |
| as much as possible | ์ต๋ํ | {specify quantitative target} |
| generally | ๋์ฒด๋ก, ์ผ๋ฐ์ ์ผ๋ก | {specify including exception conditions} |
Scoring Criteria#
| Score | Criteria |
|---|---|
| 0.0 | 0 prohibited words, all values specified |
| 0.25 | 1-2 prohibited words, most values specified |
| 0.5 | 3-5 prohibited words, some values missing |
| 0.75 | 6+ prohibited words, many values missing |
| 1.0 | Pervasive use of ambiguous expressions |
Locale coverage rule (unverified โ clear): If the spec's primary language is NOT covered by the prohibited-word table above, this dimension is UNVERIFIED, not 0.0. A keyword miss in an unsupported language must NOT be scored as "0 prohibited words" โ that silently pulls the weighted total toward CLEAR/Pass (the LANG-01 fail-open). Mark the dimension UNVERIFIED, surface a warning, and fall back to LLM semantic judgment of vagueness rather than keyword counting.
Dimension 2: Reference Clarity โ Weight 0.20#
Whether pronouns, demonstratives, and abbreviations clearly point to specific entities.
Inspection Items#
- Pronouns: "this", "that", "said" โ Replace with specific entity names
- Abbreviations: Define full name + abbreviation on first occurrence
- Implicit subjects: "is processed", "is sent" โ Specify the agent ("the server processes")
- External references: "as per existing approach" โ Specify reference document + section
Scoring Criteria#
| Score | Criteria |
|---|---|
| 0.0 | All references have 1:1 mapping, all abbreviations defined |
| 0.25 | 1-2 ambiguous references, most abbreviations defined |
| 0.5 | 3-5 ambiguous references, some abbreviations undefined |
| 0.75 | Many ambiguous references, insufficient abbreviation definitions |
| 1.0 | Key entity references unclear |
Dimension 3: Completeness โ Weight 0.20#
Whether all features have acceptance criteria (AC) and edge cases have been identified.
Inspection Items#
- Acceptance criteria: Given-When-Then AC exists for all features/requirements
- Edge cases: Boundary values, empty inputs, concurrency, timeouts identified
- Error scenarios: Failure behavior defined (retry, fallback, alerts)
- Non-functional requirements: Performance, security, accessibility criteria specified
Scoring Criteria#
| Score | Criteria |
|---|---|
| 0.0 | All features have AC + edge cases + error scenarios |
| 0.25 | 90%+ AC coverage, major edge cases identified |
| 0.5 | 70%+ AC coverage, some edge cases missing |
| 0.75 | Under 50% AC coverage, many edge cases missing |
| 1.0 | Almost no AC, edge cases not considered |
Dimension 4: Consistency โ Weight 0.20#
Whether there are no contradictions between sections and terminology is unified.
Inspection Items#
- Terminology unity: Same term used for same concept (glossary exists)
- Numeric consistency: Same values consistent throughout the document
- Logical consistency: Premises in section A and conclusions in section B do not contradict
- Priority consistency: Must/Should/May consistent across sections
Scoring Criteria#
| Score | Criteria |
|---|---|
| 0.0 | 0 contradictions, fully unified terminology |
| 0.25 | 1-2 minor inconsistencies |
| 0.5 | 3-5 inconsistencies, some terminology mixed |
| 0.75 | 1+ major contradictions, extensive terminology mixing |
| 1.0 | Multiple severe contradictions, non-unified terminology |
Dimension 5: Testability โ Weight 0.15#
Whether all requirements can be verified through automation or manual testing.
Inspection Items#
- Measurable: Pass/Fail criteria exist for all requirements
- Reproducible: Same conditions yield same results during test execution
- Independent: Each requirement can be tested individually
- Time-bound: Time limit for test completion specified (when applicable)
Scoring Criteria#
| Score | Criteria |
|---|---|
| 0.0 | All requirements are automatically testable |
| 0.25 | 90%+ testable, remainder manually verifiable |
| 0.5 | 70%+ testable |
| 0.75 | Under 50% testable |
| 1.0 | Most require subjective judgment |
Final Score Calculation#
ambiguity_score = (lexical ร 0.25) + (reference ร 0.20) + (completeness ร 0.20)
+ (consistency ร 0.20) + (testability ร 0.15)
Report Format#
## Ambiguity Evaluation Results
| Dimension | Score | Weight | Weighted Score | Key Findings |
|-----------|-------|--------|---------------|-------------|
| Lexical Precision | {0.0-1.0} | 0.25 | {calculated} | {findings} |
| Reference Clarity | {0.0-1.0} | 0.20 | {calculated} | {findings} |
| Completeness | {0.0-1.0} | 0.20 | {calculated} | {findings} |
| Consistency | {0.0-1.0} | 0.20 | {calculated} | {findings} |
| Testability | {0.0-1.0} | 0.15 | {calculated} | {findings} |
| **Total** | | | **{sum}** | **{verdict}** |
### Improvement Recommendations
1. {Specific improvement item}