requirements-clarity

Tool passed security scan

Malicious tool definition detected

Tool: README.md [2/2] Description: 1.0, or user-specified) ## Best Practices ### DO - Answer questions thoroughly but concisely - Provide examples when you have specific preferences - Ask for clarification if questions aren't clear - Review the final PRD and provide feedback - Share constraints and non-negotiables upfront ### DON'T - Rush through clarification rounds - Assume the skill knows your technical context - Skip questions that seem "obvious" - Approve PRD before reviewing thoroughly - P

Malicious tool definition detected

(KISS check) - to ensure clarity before coding. --- # 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?

Tool: SKILL.md [2/2]