skills.rest
wildbitca
wildbitcaOFFICIAL
Explore all skills by this author →
WebsiteGitHub

common-product-requirements

Guide iterative discovery and document product requirements into a PRD file.

1|Updated Mar 19, 2026
Search Tags:#templates#specification#requirements#validation#discovery#prd
One-click install
npx skills add https://github.com/wildbitca/ai-resources --skill common-product-requirements
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: common-product-requirements
Source: https://github.com/wildbitca/ai-resources/tree/main/skills/common-product-requirements
Command: npx skills add https://github.com/wildbitca/ai-resources --skill common-product-requirements

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Builds a repeatable process to gather, align, and document product requirements before work, reducing risk of scope creep and miscommunication.

Core Features & Use Cases

  • Discovery-driven: guides stakeholders through iterative questions to surface goals, constraints, and success criteria.
  • Template-based drafting: loads a PRD template from references/prd-template.md and fills it with discovered details.
  • Verification-ready deliverable: outputs a PRD at docs/specs/prd-[feature-name].md with an open questions section for follow-ups.
  • Use Case: As a PM, you run a PRD session to align engineers, designers, and stakeholders around a single spec before implementation.

Quick Start

Run a three-phase workflow: perform discovery, draft the PRD using the template, then verify and save to docs/specs/prd-[feature-name].md.

Frequently Asked Questions about common-product-requirements

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

FAQPage Schema
How do I write a product requirements document to prevent scope creep?▼

A product requirements document prevents scope creep by capturing goals, constraints, and success criteria before implementation. This skill enforces a discovery-driven workflow, guiding stakeholders through iterative questions to surface and align on complete requirements.

What is the best way to structure a PRD for feature speccing?▼

The best way to structure a PRD for feature speccing is using a standardized template. This skill loads a PRD template from its references and fills it with discovered details, outputting a verification-ready deliverable with an open questions section for follow-ups.

How do I run a PRD discovery session to align engineers and stakeholders?▼

Running a PRD discovery session involves guiding stakeholders through iterative questions to document goals and constraints. This skill facilitates a three-phase workflow: perform discovery, draft the PRD using a template, then verify and save the aligned specification.

Can I generate a PRD markdown file directly in my project specs directory?▼

Yes, you can generate a PRD markdown file directly in your project. This skill outputs the final product requirements document at docs/specs/prd-[feature-name].md, providing a verification-ready file for your engineering and design teams.

What should be included in a PRD validation checklist before development?▼

A PRD validation checklist should include confirmed goals, constraints, success criteria, and an open questions section for unresolved follow-ups. This skill enforces a structured workflow with validation checklists to ensure complete requirements are documented before feature work.

When do I need a structured PRD workflow instead of a simple feature spec?▼

You need a structured PRD workflow when reducing the risk of miscommunication and scope creep across engineers, designers, and stakeholders. This skill provides a repeatable process to gather, align, and document product requirements before committing to implementation.

Related Skills

Explore More Product & Management Skills→
co-cddoco-cddo
4

bmad-create-prd

Draft a structured PRD with Success Criteria and User Journeys from discovery materials.

Official
Advanced
thepriceisrightthepriceisright

prd

Generate a structured PRD from a feature brief and save it to tasks/prd-[feature-name].md.

Community
Advanced
jeninhjeninh

prd

Generate structured Product Requirements Documents from feature descriptions.

Community
Advanced
iamsteveholmesiamsteveholmes

intake

Capture conversation story ideas into backlog stub files with index entries.

Community
Intermediate