requirements-clarity

Malicious tool definition detected

Tool: README.md [1/2] Description: # Requirements Clarity A systematic skill for transforming vague requirements into actionable Product Requirements Documents (PRDs) through focused dialogue and iterative clarification. ## Purpose This skill helps you avoid costly misunderstandings and rework by ensuring requirements are crystal clear before implementation begins.

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

Tool: SKILL.md [1/2] Description: --- name: requirements-clarity description: 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?

Tool: SKILL.md [2/2]