What it does
The skill clarifies ambiguous requirements through focused dialogue before any code is written. It asks two core questions: "Why?", a YAGNI check on whether the feature is really needed, and "Simpler?", a KISS check on whether a simpler approach would meet the goal.
It is intended for cases where requirements are unclear, where a feature is complex (estimated at more than two days of work), or where the work needs coordination across teams.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- AI Templates (aitmpl) first seen 13 Nov 2026 · last seen 19 Nov 2026 · its page on the source · figures reported by the source: aitmpl downloads 221
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.
As shown on www.aitmpl.com when we last read it