writing-prds

Generates Product Requirements Documents with templates and acceptance criteria.

Updated Aug 27, 2026

Search Tags:#documentation #requirements #product management #user stories #feature definition #prd

Ready to run

npx skills add https://github.com/toddbadams/SBFoundation --skill writing-prds-toddbadams

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: writing-prds
Source: https://github.com/toddbadams/SBFoundation/tree/main/.claude/skills/product/writing-prds
Command: npx skills add https://github.com/toddbadams/SBFoundation --skill writing-prds-toddbadams

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation of comprehensive Product Requirements Documents (PRDs), ensuring all essential aspects of a new feature or initiative are clearly defined.

Core Features & Use Cases

Structured Document Creation: Guides users through defining goals, user stories, requirements, and scope.
Standardized Format: Utilizes a clear PRD structure and provides templates for user stories and acceptance criteria.
Use Case: When kicking off a new project, use this Skill to generate a PRD that outlines the feature's purpose, user needs, and technical specifications, ensuring alignment among stakeholders.

Quick Start

Use the writing-prds skill to draft a new product requirements document for the user profile feature.

Frequently Asked Questions about writing-prds

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

FAQPage Schema

How do I write a product requirements document for a new feature?▼

A product requirements document outlines goals, user stories, acceptance criteria, and scope for new features. It uses structured templates and best practices like INVEST criteria to ensure comprehensive documentation and stakeholder alignment.

What should be included in user stories and acceptance criteria for a PRD?▼

User stories and acceptance criteria in a PRD should include structured feature definitions and scope boundaries. Utilizing standardized templates ensures that user needs, functional specifications, and non-functional requirements are clearly captured for technical alignment.

When do I need to create a product requirements document for a project initiative?▼

You need to create a product requirements document when kicking off a new project or feature initiative. It outlines the purpose, user needs, and technical specifications to ensure alignment among stakeholders before development begins.

Does this PRD generation process support the INVEST criteria for user stories?▼

Yes, the PRD generation process supports the INVEST criteria for user stories. It facilitates defining user stories and acceptance criteria using best practices to ensure feature definition quality and structured documentation.

What is the best way to define functional and non-functional requirements for product management?▼

The best way to define functional and non-functional requirements is using a structured PRD format. This approach standardizes feature definition, scope boundaries, and technical specifications to ensure comprehensive product management documentation.

Can I draft a PRD for a user profile feature without prior product management experience?▼

Yes, you can draft a PRD without extensive product management experience. The process provides structured templates and standardized formats that guide you through defining goals, user stories, and requirements systematically.