prd

Generate structured Product Requirements Documents with user stories and acceptance criteria.

Updated Nov 23, 2025

Search Tags:#documentation #feature planning #requirements gathering #user stories #prd #product requirements

Ready to run

npx skills add https://github.com/anahelenasilva/meridiano-nestjs --skill prd-anahelenasilva

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/anahelenasilva/meridiano-nestjs/tree/main/.cursor/skills/generate-prd
Command: npx skills add https://github.com/anahelenasilva/meridiano-nestjs --skill prd-anahelenasilva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the creation of comprehensive Product Requirements Documents (PRDs), ensuring clarity and actionable specifications for new features or projects.

Core Features & Use Cases

Structured PRD Generation: Creates PRDs with Introduction, Goals, User Stories, Functional Requirements, Non-Goals, and more.
Clarifying Questions: Asks targeted questions to gather necessary details before generating the PRD.
Use Case: Planning a new feature like a "Task Priority System"? Use this Skill to generate a detailed PRD that outlines user stories, functional requirements, and acceptance criteria, ready for development.

Quick Start

Use the prd skill to create a product requirements document for a new user authentication feature.

Frequently Asked Questions about prd

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

FAQPage Schema

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

To generate a product requirements document, provide your feature concept and the tool will ask clarifying questions to outline user stories, functional requirements, and acceptance criteria. It structures the PRD with clear goals and non-goals for development planning.

What should be included in user stories and functional requirements for a PRD?▼

User stories and functional requirements in a PRD should include specific acceptance criteria and detailed instructions. This ensures the specifications are clear, actionable, and suitable for junior developers or AI agents to implement without ambiguity.

Can I use this to plan feature scope and define non-functional requirements?▼

Yes, you can use this to plan feature scope and define non-functional requirements. It specifies clear scope boundaries and outlines both functional and non-functional aspects to ensure the project planning phase captures all necessary technical constraints.

What is the best way to write an actionable PRD for junior developers?▼

The best way to write an actionable PRD for junior developers is by answering targeted clarifying questions to extract detailed specifications. This process ensures the final document provides explicit instructions, structured user stories, and clear acceptance criteria.

Does generating a PRD require any specific formatting tools or dependencies?▼

Generating a PRD requires no specific formatting tools or external dependencies. The skill operates independently to facilitate your planning by structuring the introduction, goals, and requirements directly from your provided feature details.