Speckit.clarify
bro-skills - Spec-Driven Development CLI
npx -y skills add wedabro/bro-skills --skill speckit.clarifyAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Ambiguity Resolver - Detect and resolve ambiguity in spec.
SKILL.md
1.6 KB, as published. Nobody here has run it
🎯 Mission
Scan spec.md → detect ambiguity → ask developer up to 3 questions → update spec.
📥 Input
.agent/specs/[feature]/spec.md
📋 Protocol
- Scan spec.md to find:
- Vague language: "fast", "many", "easy to use", "similar", "etc."
- Missing boundaries: Unknown min/max, pagination limits, file size limits
- Undefined error handling: What happens when X fails?
- Ambiguous actors: Who is "User"? Admin? Guest? Registered?
- Categorize each issue:
- 🔴 CRITICAL: Architectural influence, MUST ask developer
- 🟡 IMPORTANT: Should ask but can suggest default
- 🟢 MINOR: Editorial correction that cannot change behavior, such as a typo, broken reference, or inconsistent requirement ID.
- Ask the developer MAXIMUM 3 CRITICAL questions, each question has an options table:
| Option | Describe | Impact |
|---|---|---|
| A | ... | ... |
| B | ... | ... |
| C | ... | ... |
4. Auto-fix only behavior-neutral 🟢 MINOR items. Present missing limits,
permissions, defaults, and error behavior as assumptions or questions; do
not write them into the spec without approval.
5. Update spec.md with clarifications → mark `[CLARIFIED]` .
## 📤 Output
- File: Updated `.agent/specs/[feature]/spec.md`
## 🚫 Guard Rails
- MAXIMUM 3 questions — don't ask too many.
- DO NOT change the original intent of the spec.
- DO NOT invent product limits, permissions, defaults, or acceptance criteria.