requirements-clarity

Refine ambiguous feature requests into development-ready Product Requirements Documents.

9|2|Updated Jan 29, 2026

Search Tags:#planning #specification #requirements #clarification #prd #product-management

Ready to run

npx skills add https://github.com/stephanj/claude-code-collections --skill requirements-clarity-stephanj

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requirements-clarity
Source: https://github.com/stephanj/claude-code-collections/tree/main/skills/requirements-clarity
Command: npx skills add https://github.com/stephanj/claude-code-collections --skill requirements-clarity-stephanj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates ambiguity in feature requests by systematically identifying gaps in functional, technical, and business requirements, preventing costly development rework.

Core Features & Use Cases

Systematic Gap Analysis: Uses a 100-point scoring rubric to evaluate requirements across functional, technical, and business dimensions.
Iterative Clarification: Guides users through focused, progressive questioning to build context without overwhelming them.
Automated PRD Generation: Produces a comprehensive, structured Product Requirements Document once a high clarity score is achieved.

Quick Start

Invoke the requirements-clarity skill and provide your initial feature description to begin the systematic refinement process.

Frequently Asked Questions about requirements-clarity

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I turn a vague feature idea into a development-ready product specification?▼

To turn a vague idea into a product specification, you systematically refine ambiguous feature requests through iterative dialogue to identify gaps in functional and technical requirements, preventing development rework.

What is the best way to write a comprehensive PRD for complex software features?▼

The best way to write a comprehensive PRD is to evaluate your feature requirements against a 100-point rubric to ensure completeness across business dimensions before generating the final structured document.

How do I identify missing technical constraints and acceptance criteria in my feature requests?▼

You identify missing technical constraints and acceptance criteria by conducting a systematic gap analysis using focused, progressive questioning that builds context without overwhelming you.

Do I need a fully detailed feature description before starting the PRD clarification process?▼

No, you do not need a fully detailed feature description beforehand. You can provide an initial ambiguous feature description, and the systematic refinement process will guide you through progressive clarification.

Why does ambiguous feature requests cause costly development rework?▼

Ambiguous feature requests cause development rework because they contain gaps in functional, technical, and business requirements, leading to misaligned implementation that fails to meet actual product needs.

When should I use an iterative dialogue approach for product management specifications?▼

You should use an iterative dialogue approach for product management specifications when handling complex software development tasks requiring clear functional specifications, technical constraints, and acceptance criteria.