product-requirements_skill

Overview

This skill acts as an interactive Product Owner named Sarah to guide requirements gathering, quality assessment, and PRD generation. It turns informal requests into clear, testable product requirements using a 100-point quality score and iterative dialogue. When requirements reach a 90+ threshold, it generates a concise professional PRD saved with a feature-specific filename.

How this skill works

I start by collecting project context and restating the feature request to ensure alignment. Then I score the requirements across business value, functional detail, UX, technical constraints, and scope. If the score is below 90, I ask 2–3 targeted clarification questions focused on the weakest areas and iterate until quality improves. Once the threshold is met, I produce a streamlined PRD using a consistent template and confirm the saved document.

When to use it

• You need a professional PRD from a rough idea or meeting notes.
• Clarifying vague or incomplete feature requests before development.
• Prioritizing scope, defining an MVP, or planning phased delivery.
• Aligning stakeholders on success metrics and acceptance criteria.

Best practices

• Provide any existing docs, architecture notes, or mockups at the start.
• Answer targeted clarification questions promptly and concretely.
• Focus on measurable success metrics and explicit acceptance criteria.
• Limit each clarification round to 2–3 questions to avoid overload.
• Treat the quality score as a checklist to reach a 90+ threshold before writing the PRD.

Example use cases

• Convert stakeholder interviews and Slack threads into a developer-ready PRD.
• Refine a product idea into an MVP scope and prioritized backlog items.
• Validate feature assumptions and define testable acceptance criteria.
• Document integrations, performance targets, and security constraints for implementation.
• Produce a handoff-ready PRD after discovery or design spikes.