prd

Generate a structured PRD from a feature prompt and save it to a Markdown file.

114|13|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/jellydn/my-ai-tools --skill prd-jellydn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/jellydn/my-ai-tools/tree/main/skills/prd
Command: npx skills add https://github.com/jellydn/my-ai-tools --skill prd-jellydn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning and aligning on new features is often manual, error-prone, and time-consuming. This skill automates the creation of a structured PRD so teams share a clear, implementable plan.

Core Features & Use Cases

  • Generate a complete PRD from a feature prompt, including goals, success criteria, user stories, and acceptance criteria.
  • Automatically prompt for 3-5 clarifying questions to resolve ambiguity and produce a high-quality PRD.
  • Save the resulting PRD to tasks/prd-[feature-name].md and reuse templates for consistency.

Quick Start

Activate the PRD skill and provide a feature description. The skill will ask clarifying questions and then generate a single PRD file at tasks/prd-[feature-name].md.

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 from a feature prompt?

To generate a product requirements document, provide a feature prompt and the skill asks 3-5 clarifying questions to resolve ambiguity, then outputs a PRD with acceptance criteria to tasks/prd-[feature-name].md.

What sections should be included in a structured PRD for software development?

A structured PRD includes Introduction, Goals, User Stories, Functional Requirements, Non-Goals, Design Considerations, Technical Considerations, Success Metrics, and Open Questions with verifiable acceptance criteria.

How do I ensure my user stories have explicit and verifiable acceptance criteria?

To ensure user stories have verifiable acceptance criteria, the PRD generation process enforces a strict format requiring explicit, testable conditions for each story within the saved markdown file.

Can I automate writing PRDs and save them directly to my project tasks folder?

Yes, you can automate writing PRDs by activating the skill with a feature description, which automatically formats and saves the resulting document directly to tasks/prd-[feature-name].md.

What is the best way to define non-goals and success metrics for product planning?

The best way to define non-goals and success metrics is through a guided PRD template that enforces dedicated sections for both, ensuring clear boundaries and measurable outcomes for product planning.

Does generating a PRD require any prerequisite templates or dependencies?

No prerequisite templates or dependencies are required; the skill reuses its own internal templates to automatically produce a consistent, structured PRD from your feature description.