Skip to content

req-ambiguity-detection

Domain: req · Model class: free

Use this skill when the user wants to work on Identifying underspecified, conflicting, or ambiguous requirements before implementation. Triggers include “find ambiguities in this spec”, “what is unclear in these requirements”, “flag missing constraints”. Do NOT use when extract the requirements first (use core-requirements-analysis).

Identifying underspecified, conflicting, or ambiguous requirements before implementation. This skill provides structured guidance, references, and worked examples to help produce high-quality, actionable outputs.

  • “find ambiguities in this spec”
  • “what is unclear in these requirements”
  • “flag missing constraints”
  • “surface hidden assumptions”
  • extract the requirements first (use core-requirements-analysis)
  • clarify scope (use core-scope-clarification)
  1. What is the user’s goal and current state?
  2. What constraints (time, team, compliance) apply?
  3. Are there existing artifacts (specs, code, benchmarks) to reference?
  • structured requirements
  • constraints or acceptance criteria
  • scope boundaries
  • prioritized next actions

req-analysis · req-scope