requirements-clarity

Solid

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.

AI & Automation 1,931 stars 178 forks Updated 2 months ago MIT

Install

View on GitHub

Quality Score: 88/100

Stars 20%
100
Recency 20%
75
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Requirements Clarity Skill ## Description Automatically transforms vague requirements into actionable PRDs through systematic clarification with a 100-point scoring system. ## Instructions When invoked, detect vague requirements: 1. **Vague Feature Requests** - User says: "add login feature", "implement payment", "create dashboard" - Missing: How, with what technology, what constraints? 2. **Missing Technical Context** - No technology stack mentioned - No integration points identified - No performance/security constraints 3. **Incomplete Specifications** - No acceptance criteria - No success metrics - No edge cases considered - No error handling mentioned 4. **Ambiguous Scope** - Unclear boundaries ("user management" - what exactly?) - No distinction between MVP and future enhancements - Missing "what's NOT included" **Do NOT activate when**: - Specific file paths mentioned (e.g., "auth.go:45") - Code snippets included - Existing functions/classes referenced - Bug fixes with clear reproduction steps ## Core Principles 1. **Systematic Questioning** - Ask focused, specific questions - One category at a time (2-3 questions per round) - Build on previous answers - Avoid overwhelming users 2. **Quality-Driven Iteration** - Continuously assess clarity score (0-100) - Identify gaps systematically - Iterate until ≥ 90 points - Document all clarification rounds 3. **Actionable Output** - Generate concrete s...

Details

Author
softaworks
Repository
softaworks/agent-toolkit
Created
4 months ago
Last Updated
2 months ago
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Web & Frontend Solid

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.

27,705 Updated today
davila7
AI & Automation Listed

neo-clarification

Use this skill when the user gives vague, emotional, fragmented, screenshot-based, or complaint-style requirements and wants them converted into structured specs, acceptance criteria, or clarifying questions.

5 Updated yesterday
Benknightdark
AI & Automation Listed

deep-clarify

Clarifies ambiguous requests through Socratic dialogue, drawing out goals, completion criteria, and constraints to produce a structured spec document. Pre-dispatch requirement clarification step for agent dispatch. Triggered by "I don't know what to build", "how should I approach this", "organize this for me", "clarify this", "deep-clarify".

2 Updated today
chrono-meta
AI & Automation Listed

deep-clarify

Clarifies ambiguous requests through Socratic dialogue, drawing out goals, completion criteria, and constraints to produce a structured spec document. Pre-dispatch requirement clarification step for agent dispatch. Triggered by "I don't know what to build", "how should I approach this", "organize this for me", "clarify this", "deep-clarify".

2 Updated today
chrono-code
Code & Development Listed

swing-clarify

Prevents premature execution on ambiguous requests. Analyzes request clarity using 5W1H decomposition, surfaces hidden assumptions, and generates structured clarifying questions before work begins. Use at the start of any non-trivial task, or when a request could be interpreted multiple ways. Triggers on "뭘 원하는건지", "요구사항 정리", "clarify", "what exactly", "scope", "requirements", "정확히 뭘", "before we start".

36 Updated 1 months ago
TheStack-ai