skills.rest
dakotahp
dakotahpCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

product-requirements

Generate a product requirements document with goals, user stories, and acceptance criteria.

Updated Aug 14, 2012
Search Tags:#prd#product-management#user-stories#acceptance-criteria#feature-spec#product-requirements
One-click install
npx skills add https://github.com/dakotahp/dotfiles --skill product-requirements-dakotahp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-requirements
Source: https://github.com/dakotahp/dotfiles/tree/main/dot_config/claude/skills/product-requirements
Command: npx skills add https://github.com/dakotahp/dotfiles --skill product-requirements-dakotahp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts informal feature ideas or briefs into a clear, actionable product requirements document that reduces ambiguity, prevents rework, and enables engineering to build without follow-up clarification.

Core Features & Use Cases

  • Clarify missing details: Detect missing critical inputs (at minimum "What" and "Who") and ask a single targeted clarification question when needed.
  • Structured PRD output: Produce a full PRD with Problem Statement, Goals, Non-Goals, User Stories, Acceptance Criteria, Open Questions, and Out of Scope notes and save it to docs/plans/YYYY-MM-DD-<slugified-feature-name>.md.
  • Developer-ready acceptance criteria: Write binary, testable acceptance criteria and countable user stories so engineers can implement features with minimal follow-up.

Quick Start

Write a PRD for a feature that lets visitors view a freelancer's public profile showing name, bio, listed services, and a contact button.

Frequently Asked Questions about product-requirements

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

FAQPage Schema
How do I turn a feature idea into a developer-ready PRD with user stories and acceptance criteria?▼

To turn a feature idea into a developer-ready PRD, provide a brief and the tool generates a structured document with Problem Statements, measurable Goals, Non-Goals, countable User Stories, and binary Acceptance Criteria.

What is the best way to write binary acceptance criteria for a product requirements document?▼

Writing binary acceptance criteria for a product requirements document involves creating testable, true/false conditions for each feature, ensuring engineers can implement the functionality with minimal follow-up clarification.

How do I structure non-goals and open questions in a feature spec?▼

Structuring non-goals and open questions in a feature spec requires listing at least two explicit non-goals to define boundaries, alongside an open questions table to track unresolved project ambiguities.

Can I automatically save a generated product requirements document to a specific markdown file path?▼

Yes, the generated product requirements document is automatically saved as a markdown file using the structured path docs/plans/YYYY-MM-DD-<slugified-feature-name>.md to maintain organized project planning.

What happens if my feature brief is missing critical inputs for the PRD?▼

If a feature brief is missing critical inputs like the target user or feature action, the tool detects the gap and asks a single targeted clarification question to ensure the PRD is complete.

Related Skills

Explore More Product & Management Skills→
qa-amanqa-aman
19

write-prd

Draft a structured PRD from a brief or problem statement.

Community
Advanced
jonkraatzjonkraatz

feature

Create feature roadmaps, PRDs, and issue tickets from ideas.

Community
Advanced
sibukixxxsibukixxx

business-to-requirements

Transform vague business ideas into structured technical requirements and user stories.

Community
Advanced
IntegralistIntegralist
2

to-spec

Generate a specification document with requirements, acceptance criteria, and testing approach.

Community
Advanced