requirements-clarity
Clarify ambiguous requirements through focused dialogue before implementation. Use when requirements are unclear, features are complex (>2 days), or involve cross-team coordination. Ask two core questions - Why? (YAGNI check) and Simpler? (KISS check) - to ensure clarity before coding.
76
1.63x
Quality
62%
Does it follow best practices?
Impact
100%
1.63xAverage score across 3 eval scenarios
Securityby
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/requirements-clarity/SKILL.mdNo security issues found
Scanned
- Repository
- softaworks/agent-toolkit
- Commit
3027f20
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.