home / skills / richtabor / agent-skills / create-prd

create-prd skill

safe

This skill helps you create a PRD interactively, asking clarifying questions and generating a detailed document for feature planning.

npx playbooks add skill richtabor/agent-skills --skill create-prd

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.0 KB

---
name: create-prd
description: Plan features interactively. Asks clarifying questions, then generates a detailed PRD document.
---

# Create PRD

Generate a Product Requirements Document through interactive planning.

## Process

### 1. Understand the Feature

Read the user's feature request. If unclear, ask for a brief description.

### 2. Ask Clarifying Questions

Ask 3-5 clarifying questions to understand scope and requirements.

Format with lettered options:
```
1. Who is the primary user?
   A) Logged-in users only
   B) All visitors
   C) Admin users

2. Should this persist across sessions?
   A) Yes, save to database
   B) No, session only
```

User can respond with combinations like "1A, 2B".

### 3. Generate PRD

After answers, create a detailed PRD with these sections:

```md
# PRD: [Feature Name]

## Introduction
Brief overview of the feature and why it's needed.

## Goals
- Primary goal
- Secondary goals

## User Stories
### [Story Title]
**Description:** As a [user], I want [action] so that [benefit].
**Acceptance Criteria:**
- [ ] Specific, verifiable criterion
- [ ] Another criterion
- [ ] Typecheck passes
- [ ] (UI changes) Verify in browser

## Functional Requirements
1. Requirement one
2. Requirement two

## Non-Goals
What this feature explicitly won't do.

## Design Considerations
UI/UX notes, mockup descriptions.

## Technical Considerations
Architecture notes, dependencies, potential challenges.

## Success Metrics
How to measure if this feature is successful.

## Open Questions
Any unresolved decisions.
```

### 4. Save PRD

Save to `prds/[feature-name].md` (create `prds/` directory if needed).

```
PRD saved to prds/[feature-name].md

Next: Run /create-prd-json to convert to executable format.
```

## Guidelines

- Be explicit and unambiguous
- Write for junior developers and AI agents
- Avoid jargon
- Number requirements for easy reference
- Acceptance criteria must be verifiable, not vague
  - Good: "Button displays 'Save' text"
  - Bad: "Button looks good"

Overview

This skill plans product features interactively and generates a detailed Product Requirements Document (PRD). It asks targeted clarifying questions, accepts compact option-style answers, and produces a structured, developer-ready PRD file. The output is explicit, verifiable, and written for junior engineers and automation.

How this skill works

The skill first reads a user feature request and, when needed, prompts 3–5 clarifying multiple-choice questions formatted with numbered prompts and lettered options. The user replies with combined selections (for example, "1A, 2B") and the skill uses those answers to assemble a full PRD with sections like Goals, User Stories, Functional Requirements, Design and Technical Considerations, Metrics, and Open Questions. Finally, it saves the PRD to a file path under prds/[feature-name].md and confirms the next step to convert it into executable format.

When to use it

You need a complete PRD for a new feature before engineering work begins.
You want clearly verifiable acceptance criteria for QA or automation.
You need a living document that junior developers or AI agents can implement from.
You want to align stakeholders with explicit goals and non-goals.
You prefer an interactive planning flow to refine scope quickly.

Best practices

Provide a concise initial feature request to speed the Q&A step.
Answer clarifying questions using the numbered/lettered format (e.g., "1A, 2B") to avoid ambiguity.
Keep acceptance criteria specific and testable (UI text, API responses, state changes).
Number functional requirements to make task breakdown and tracking easier.
Review and update the saved PRD file path and file name for clarity before sharing.

Example use cases

Drafting a PRD for a new onboarding flow that must persist across sessions.
Creating requirements for an admin-only reporting dashboard with specific metrics.
Defining an MVP for a file-sharing feature with clear success metrics.
Converting product manager notes into a developer-ready PRD for sprint planning.
Standardizing PRDs across multiple small features for consistent QA criteria.

FAQ

How many clarifying questions will I be asked?

Typically 3–5 questions focused on scope, users, persistence, and critical constraints.

What format should I use to answer the questions?

Reply using the numbered prompt and lettered option format (for example, "1A, 2B, 3C").

Where is the PRD saved?

The skill saves the PRD to prds/[feature-name].md and returns a confirmation message with the path.