ambiguity-detector
Detects and analyzes ambiguous language in software requirements and user stories. Use when reviewing requirements documents, user stories, specifications, or any software requirement text to identify vague quantifiers, unclear scope, undefined terms, missing edge cases, subjective language, and incomplete specifications. Provides detailed analysis with clarifying questions and suggested improvements.
npx skills add majiayu000/claude-skill-registry --skill ambiguity-detector --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Ambiguity Detection in Software Requirements You are an expert requirements analyst who identifies and resolves ambiguities in software requirements. ## Core Capabilities This skill enables you to: 1. **Detect ambiguity patterns** - Identify 10 categories of ambiguous language 2. **Assess severity** - Classify ambiguities by impact (critical, high, medium, low) 3. **Generate clarifying questions** - Produce targeted questions to resolve ambiguities 4. **Suggest improvements** - Provide clear, testable alternatives 5. **Create reports** - Generate structured analysis with actionable recommendations ## Analysis Workflow Follow this process when analyzing requirements for ambiguity: ### Step 1: Read Requirements Thoroughly Read each requirement statement and identify: - Core intent and purpose - Actors and entities involved - Actions and behaviors described - Constraints and conditions - Success criteria ### Step 2: Scan for Ambiguity Patterns Use `references/ambiguity_patterns.md` to systematically check for: **1. Vague Quantifiers** - Words: "many", "few", "some", "several", "enough", "reasonable" - Flag: Any imprecise quantity without numeric specification **2. Temporal Ambiguity
- Core Capabilities
- Analysis Workflow
- Step 1: Read Requirements Thoroughly
- Step 2: Scan for Ambiguity Patterns
- Step 3: Classify Severity
- Step 4: Generate Clarifying Questions
- Step 5: Provide Alternative Phrasings
- Step 6: Create Analysis Report
- Output Formats
- Best Practices
- Common Pitfalls to Avoid
- Example Analysis
- Resources
What does the ambiguity-detector skill do?
Detects and analyzes ambiguous language in software requirements and user stories. Use when reviewing requirements documents, user stories, specifications, or any software requirement text to identify vague quantifiers, unclear scope, undefined terms, missing edge cases, subjective language, and incomplete specifications. Provides detailed analysis with clarifying questions and suggested improvements.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill ambiguity-detector --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.