Skip to content
Skills Library
Management & product · Writing

write-prd

/write-prd

Write a practical Product Requirements Document (PRD) from a product idea, feature concept, customer request, business problem, or rough product opportunity. Use when the user asks to write, draft, create, generate, or save a PRD, product requirements document, product spec, feature requirements, 产品需求文档, 产品方案, 需求说明, or PRD from an idea. Output a diagram-rich Markdown PRD under the current project's markdown/ directory.

Repository
blog ↗
Licence
LGPL
Last repository change
21.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 21.10.2026, without references to retired models or APIs.

Licence

LGPL, otwarta.

What it does and when to use it

Write a practical Product Requirements Document (PRD) from a product idea, feature concept, customer request, business problem, or rough product opportunity. Use when the user asks to write, draft, create, generate, or save a PRD, product requirements document, product spec, feature requirements, 产品需求文档, 产品方案, 需求说明, or PRD from an idea. Output a diagram-rich Markdown PRD under the current project's markdown/ directory.

Original author description

Write a practical Product Requirements Document (PRD) from a product idea, feature concept, customer request, business problem, or rough product opportunity. Use when the user asks to write, draft, create, generate, or save a PRD, product requirements document, product spec, feature requirements, 产品需求文档, 产品方案, 需求说明, or PRD from an idea. Output a diagram-rich Markdown PRD under the current project's markdown/ directory.

How it works

  1. Core Rule
  2. Inputs
  3. Workflow
  4. Output Requirements
  5. Quality Bar
  6. Reference
Original SKILL.md headings · 99 lines, 774 words
SKILL.md preview
---
name: write-prd
description: Write a practical Product Requirements Document (PRD) from a product idea, feature concept, customer request, business problem, or rough product opportunity. Use when the user asks to write, draft, create, generate, or save a PRD, product requirements document, product spec, feature requirements, 产品需求文档, 产品方案, 需求说明, or PRD from an idea. Output a diagram-rich Markdown PRD under the current project's markdown/ directory.
---

# Write PRD

## Core Rule

Turn the user's idea into a PRD that helps a team decide, build, test, launch, and review the product work. A good PRD is not a feature list; it is a clear product bet:

`problem -> user -> goal -> evidence -> scope -> behavior -> acceptance -> launch validation`

Save the final PRD as Markdown under the current project's `markdown/` directory. Create the directory if missing.

## Inputs

Use the user's prompt as the source idea. If the prompt is vague, infer conservatively and write assumptions explicitly in the PRD. Ask a clarification question only when the missing information would materially change the product direction, such as target user, business domain, or platform.

If the user provides source notes, meeting records, screenshots, tickets, links, or existing docs, use them as evidence. If current market, competitor, pricing, regulation, or live product data is required and not provided, verify with reliable sources before using specific claims.

## Workflow

1. **Normalize the idea**
   - Identify the product/domain, target user, triggering scenario, problem, proposed solution, and expected business outcome.
   - Separate user problem from requested solution. For example, "export Excel" may mean reporting, sharing, audit, migration, or offline analysis.
   - Name the PRD topic in a short Chinese or English slug.

2. **Build the product argument**
   - Write a one-sentence product bet: "For [user], in [scenario], solve [problem], by [solution], measured by [metric]."
   - State assumptions when evidence is absent.
   - Include existing alternatives or workarounds; a new product competes with the user's current behavior.
   - Define goals and non-goals before writing feature details.

3. **Design the PRD structure**
   - Read `references/prd-template.md` when drafting the document.
   - Keep sections practical. Do not pad with generic market background.
   - Scale detail with risk: simple internal tools can be concise; payment, data, permission, compliance, AI, or customer-facing flows need stronger edge cases and acceptance criteria.

4. **Add diagrams**
   - Include at least one useful diagram.
   - Prefer Mermaid for workflows, user journeys, state transitions, data flow, decision trees, and metric chains.
   - ASCII text is acceptable for simple state tables or wireframe sketches.
   - If using SVG, output the `.svg` file separately in `markdown/` and reference it from the PRD with a relative Markdown image link, for example `![流程图](prd-topic-flow-20260609.svg)`.
   - Diagrams must support reasoning; do not add decorative graphics.

5. **Write feature requirements**
   - For each major capability, cover: user story, main path, edge cases, permissions, data rules, system behavior, analytics/events, and acceptance criteria.
   - Do not prescribe technical architecture unless the user asks. Product should define behavior, constraints, and verification, not implementation internals.
   - For AI features, specify input, output, quality bar, editability, failure modes, human review, data retention, and safety boundaries.

6. **Define validation**
   - Include result metrics, process metrics, and guardrail metrics.
   - Define launch plan, rollout scope, rollback conditions, and post-launch review timing.
   - Include stop conditions: what evidence means the team should stop, rollback, or change hypothesis.

7. **Save and verify**
   - File name: `markdown/<topic>-prd-<YYYYMMDD>.md`.
   - If SVG diagrams are created, use `markdown/<topic>-<diagram-name>-<YYYYMMDD>.svg`.
   - After writing, verify the Markdown file exists and includes a diagram, goals/non-goals, requirements, acceptance criteria, metrics, launch plan, and open questions.

## Output Requirements

The PRD must be written in Chinese unless the user asks for another language.

The final Markdown should be complete enough for product, design, engineering, testing, and business stakeholders to review. Use tables where they improve scanning, but do not hide weak reasoning in tables. Use concrete defaults for missing details and mark them as assumptions.

Required sections:

- Title and metadata
- One-sentence product bet
- Background and problem
- Target users and scenarios
- Evidence and assumptions
- Goals and non-goals
- Scope and release slicing
- User journey or workflow diagram
- Functional requirements
- Edge cases and constraints
- Data, permissions, analytics, and observability
- Acceptance criteria
- Launch, rollout, rollback, and review plan
- Metrics: result, process, guardrail
- Open questions and risks

## Quality Bar

Before finishing, check:

- Does the PRD say who has the problem, in what scenario, and why now?
- Does it distinguish user problem, product solution, and business outcome?
- Does it include current alternatives or workarounds?
- Does it define what is out of scope?
- Can engineering derive tasks without guessing core behavior?
- Can testing derive normal, abnormal, permission, and data-boundary cases?
- Can the team review success 2 to 8 weeks after launch?
- Is there at least one useful diagram?
- Is the file saved under the current project's `markdown/` directory?

## Reference

- `references/prd-template.md` - PRD structure, section guidance, and reusable table patterns.
Files in this package (3)
  • SKILL.md 6 KB
  • agents/openai.yaml 1 KB
  • references/prd-template.md 5 KB

Versions

RepositoryScoreLicence
This page · digoal/blog100LGPL
yonatangross/orchestkit100MIT
genkovich/sdlc100MIT
digoal/blog100LGPL
RizwanZafaris/product-manager-OS100MIT
max4c/skills100MIT
Mosin112/pm-harness90MIT

Database snapshot: 13.11.2026 · package version a76f744f6efd (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100write-brd
    Write a practical Business Requirements Document (BRD) from a product idea, feature concept, customer request, business problem, or rough product opportunity. Use when the user asks to write, draft, generate, refine, or save a BRD/business requirements document/product business…
  • 100write-spec
    Write a feature spec or PRD from a problem statement or feature idea. Use when creating product requirements documents.
  • 90product-spec
    Write a product requirements document (PRD) or feature spec. Use when the user describes a feature or product idea and asks for a spec, PRD, requirements, user stories, "scope this", or something to hand to engineers or designers.
  • 100create-prd
    This skill should be used when the user asks to "create PRD", "write product requirements document", or mentions "PRD", "product requirements document".
  • 100prd
    Interview the user and write a Product Requirements Document at docs/PRD.md (or docs/prd/<name>.md for a feature) — problem, scope, user types, key flows, success criteria, risks. Use when the user wants to write a PRD, scope a product or feature, capture requirements or success…
  • 100prd
    Use this skill whenever a user asks to write a PRD, create a PRD, draft a PRD, spec out a feature, or create a one-pager. Triggers include: "write a PRD", "create a PRD", "draft a PRD", "PRD for [feature]", "spec out [feature]", "one pager for [feature]", or any request to…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.