ambiguity-detector

Name: ambiguity-detector
Availability: InStock
Author: ArabelaTso

Detect ambiguous language in software requirements and user stories.

142|14|Updated Feb 14, 2026

Search Tags:#requirements #specifications #analysis #clarification #ambiguity #user stories

Ready to run

npx skills add https://github.com/ArabelaTso/Skills-4-SE --skill ambiguity-detector

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ambiguity-detector
Source: https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/ambiguity-detector
Command: npx skills add https://github.com/ArabelaTso/Skills-4-SE --skill ambiguity-detector

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill identifies and helps resolve ambiguities in software requirements, ensuring clarity and preventing costly misunderstandings during development.

Core Features & Use Cases

Ambiguity Detection: Pinpoints vague language, undefined terms, and incomplete specifications.
Severity Assessment: Classifies ambiguities by their impact (Critical, High, Medium, Low).
Clarification Generation: Creates targeted questions and suggests improved requirement phrasing.
Use Case: When reviewing user stories, use this Skill to automatically flag phrases like "as soon as possible" or "handle many users" and get specific questions to define these terms precisely.

Quick Start

Use the ambiguity-detector skill to analyze the provided requirements document for any unclear language.

Frequently Asked Questions about ambiguity-detector

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I detect vague quantifiers and unclear language in software requirements?▼

Assess ambiguity severity by classifying detected issues into Critical, High, Medium, and Low impact levels, which prioritizes which vague quantifiers or incomplete specifications require immediate clarification before development.

What is the best way to analyze incomplete specifications in user stories?▼

The best way to analyze incomplete specifications in user stories is to identify implicit assumptions and undefined terms, then automatically generate improved requirement phrasing and specific questions to define those terms precisely.

Can I generate clarifying questions for temporal ambiguity in requirements documents?▼

You can generate clarifying questions for temporal ambiguity by scanning requirements documents for phrases like "as soon as possible", flagging them, and producing specific questions to define those timeline expectations precisely.

Does the ambiguity analysis work for undefined terms and unclear scope in specifications?▼

The ambiguity analysis works for undefined terms and unclear scope in specifications by matching text against predefined templates to identify missing edge cases and unclear references, outputting severity assessments and suggested improvements.