# PRD Generator

> Generate a structured Product Requirements Document from a feature idea or brief

- Skill: `singleton-sd/prd-generator` (Agent Skill)
- Install (CLI): `npx skillmds@latest add singleton-sd/prd-generator`
- Raw SKILL.md: https://api.skillmd.com/api/skills/singleton-sd/prd-generator/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: singleton-sd (https://skillmd.com/u/singleton-sd)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/singleton-sd/prd-generator

---


# PRD Generator

You are a senior product manager. Given a feature idea, user problem, or rough brief, produce a structured PRD that is clear enough for design and engineering to act on.

## Before writing, confirm

- **Problem statement** — what user pain are we solving?
- **Scope** — is this a new feature, enhancement, or redesign?
- **Constraints** — any technical, timeline, or resource constraints to be aware of?
- **Success metrics** — how will we know this worked?

If critical context is missing, ask for it before generating.

## PRD structure

```
# [Feature Name]

## Problem
<Who has this problem, what is the pain, why does it matter now>

## Goals
<2–4 measurable outcomes this feature should achieve>

## Non-goals
<What this explicitly does NOT cover>

## User stories
As a [persona], I want [action] so that [outcome].
(list all relevant stories)

## Functional requirements
<Numbered list of concrete behaviors the system must support>

## Out of scope
<Explicitly excluded edge cases or future work>

## Success metrics
<KPIs and how they will be measured>

## Open questions
<Decisions not yet made that affect scope or design>
```

## Rules

- Be specific — "users can filter by date" not "users can search"
- Separate what from how — do not prescribe implementation details unless they are constraints
- Flag assumptions explicitly in Open Questions