refining-requirements

This skill reads your initial requirements or PRD and generates a complete, implementation-ready specification through structured questioning. It identifies ambiguities, surfaces edge cases, and outputs a formatted requirements document with validation rules ready for design and development teams.

Requirements clarification requires targeted questions across scope, user workflows, acceptance criteria, and edge cases. This skill applies a guided Q&A process to surface gaps in rough specs, PRDs, and app ideas, generating detailed answers that pin down what needs to be built and how to validate it.

Yes. This skill applies to rough ideas, PRDs, and specs across product management, UX design, and engineering planning. It generates implementation-ready requirements aligned with standardized templates, making output usable by design and development teams immediately.

Structured questioning systematically surfaces ambiguities by asking about workflows, constraints, edge cases, and validation criteria that rough specs typically skip. This skill automates that process, transforming incomplete requirements into complete specifications with acceptance criteria and known limitations.

Once you have a detailed, implementation-ready requirements document, the next step is moving into design and planning—translating requirements into wireframes, user flows, or tickets for development. Refined requirements serve as the foundation for those downstream activities.