prd

Generate a structured Product Requirements Document from a feature description.

9|1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/CarbeneAI/Forge --skill prd-carbeneai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/CarbeneAI/Forge/tree/main/.claude/skills/prd
Command: npx skills add https://github.com/CarbeneAI/Forge --skill prd-carbeneai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams and developers often receive vague feature requests that lack clear goals, acceptance criteria, and scope; this skill turns a feature idea into a precise, actionable Product Requirements Document so work can be implemented reliably.

Core Features & Use Cases

  • Clarifying Questions: Prompts the user with 3–5 targeted, lettered questions to resolve ambiguity before drafting.
  • Structured PRD Output: Produces a markdown PRD with Introduction, Goals, User Stories with verifiable acceptance criteria, Functional Requirements, Non-Goals, Design/Technical Considerations, Success Metrics, and Open Questions.
  • Artifact Saving: Guides saving the resulting PRD to tasks/prd-[feature-name].md for immediate tracking.
  • Use Case: Turn a stakeholder note like "add recurring billing" into a scoped PRD with user stories, acceptance checks, and measurable success metrics.

Quick Start

Create a PRD for a feature that lets users duplicate and share project templates across teams.

Frequently Asked Questions about prd

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

FAQPage Schema
How do I write a product requirements document from a vague feature request?

To write a product requirements document from a vague request, the Skill asks targeted clarifying questions to resolve ambiguity, then generates structured PRD sections including goals, user stories, and functional requirements.

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

User stories and acceptance criteria in a PRD should include actionable narrative descriptions alongside verifiable, testable checks that confirm the feature functions as intended and meets stakeholder needs.

How do I scope project features and define non-goals for product planning?

To scope project features and define non-goals for product planning, the Skill translates stakeholder needs into an implementation-ready markdown file that explicitly separates functional requirements from out-of-scope items.

Can I automatically generate success metrics and technical considerations for a new feature?

Yes, you can generate success metrics and technical considerations for a new feature. The Skill produces structured PRD sections that define measurable success criteria and outline relevant design constraints.

What is the best way to format a PRD for developer implementation tracking?

The best way to format a PRD for implementation tracking is using structured markdown. The Skill saves the output as a markdown file in tasks/prd-[feature-name].md, ensuring immediate project tracking and accessibility.

Does this PRD generator handle stakeholder notes lacking clear scope?

Yes, this PRD generator handles stakeholder notes lacking clear scope by prompting the user with 3-5 lettered clarifying questions to resolve ambiguity before drafting the final document.