requirements-clarity

The Requirements Clarity skill is designed for developers and product managers who need to transform vague feature requests into structured, actionable specifications. By acting as a proactive technical analyst, this skill detects ambiguity, missing technical context, and incomplete specifications in initial user prompts. It utilizes a 100-point scoring rubric to quantify project clarity across four dimensions: functional scope, technical specificity, implementation completeness, and business context. The goal is to achieve a score of 90 or above, ensuring that every task is well-defined before a single line of code is written, thereby reducing rework and technical debt.

• Systematic Assessment: Uses a 100-point rubric to evaluate requirements based on functional, technical, implementation, and business criteria.

• Proactive Dialogue: Facilitates focused, multi-round questioning to uncover edge cases, error handling requirements, and scalability constraints.

• PRD Generation: Automatically produces comprehensive Markdown-based Product Requirements Documents (PRDs) stored in local project paths.

• Iterative Refinement: Tracks clarity scores in real-time, providing feedback on which aspects of the request remain ambiguous until the requirements meet production standards.

• Context-Aware Filtering: Intelligently skips activation for well-defined tasks, bug fixes with reproduction steps, or requests containing existing code snippets, ensuring it only intervenes when necessary.

• Use this skill when dealing with high-level features that lack implementation details or when complex tasks exceed a 2-day development estimation.

• Provide a raw feature request and let the agent guide you through the refinement process until the document reaches the 90-point benchmark.

• Ensure the working directory contains a ./docs/prds/ folder where the generated specifications will be saved.

• Ideal for cross-team coordination where clear, objective definitions of success and acceptance criteria are required.

• Avoid using this skill for trivial tasks or well-documented technical refinements to keep the development workflow efficient.