When should I activate the Ambiguity Detection skill?

Activate it whenever you are analyzing a ticket for completeness, generating questions for a ticket reporter, or when a task feels underspecified.

How does this skill detect ambiguity in requirements?

It uses a multi-interpretation analysis method, generating 2-3 plausible interpretations for a requirement. If interpretations diverge significantly in implementation impact, it flags the item as ambiguous.

What kind of 'vague quantifiers' can it identify?

It flags subjective terms like 'fast', 'many', 'most', or 'standard' and prompts for specific metrics like latency thresholds, user counts, or specific versioning.

Does it detect missing edge cases?

Absolutely. It specifically looks for missing error handling, such as server failures, malformed files, or validation errors that are often omitted in initial ticket descriptions.

Can it help me communicate better with non-technical product managers?

Yes, the skill includes specific guidelines for writing non-technical questions that provide concrete options (A/B/C) to reduce back-and-forth communication.

Requirement Ambiguity Detector

Name: Requirement Ambiguity Detector
Author: Ascend-Digital

byAscend-Digital

0•

협업 도구

Identifies contradictions, vague quantifiers, and missing logic in Jira tickets to ensure implementation clarity and prevent development rework.

The Requirement Ambiguity Detector enhances Claude's ability to scrutinize technical requirements and project specifications for hidden gaps or contradictions. By employing a multi-interpretation analysis, it systematically identifies vague quantifiers, implicit assumptions, and missing error-handling logic that often lead to development delays. This skill is essential for developers and product managers who need to translate high-level requests into concrete, actionable implementation plans while minimizing back-and-forth communication through structured, non-technical clarifying questions that prioritize implementation impact.

주요 기능

01Cross-repo impact analysis for complex system architectures

02Identification of missing error-handling and edge-case boundaries

03Automated generation of non-technical clarifying questions for stakeholders

040 GitHub stars

05Multi-interpretation analysis to identify divergent implementation paths

06Detection of vague quantifiers such as 'fast', 'many', or 'most'

사용 사례

01Generating structured A/B/C option lists for product managers to clarify vague requests

02Scrutinizing new Jira tickets before starting development to prevent project scope creep

03Auditing technical documentation for implicit assumptions and boundary conditions

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add ascend-digital/claude-plugins ambiguity-detection

For use in Claude.ai and ChatGPT

주요 기능

01Cross-repo impact analysis for complex system architectures

02Identification of missing error-handling and edge-case boundaries

03Automated generation of non-technical clarifying questions for stakeholders

040 GitHub stars

05Multi-interpretation analysis to identify divergent implementation paths

06Detection of vague quantifiers such as 'fast', 'many', or 'most'

사용 사례

01Generating structured A/B/C option lists for product managers to clarify vague requests

02Scrutinizing new Jira tickets before starting development to prevent project scope creep

03Auditing technical documentation for implicit assumptions and boundary conditions