# Create Confirmation-Driven PRDs

PRD work often becomes vague, unconfirmed, or hard to hand off. This skill guides structured discovery, story confirmation, diagrams, and final PRD generation.

## Install

```bash
npx skillstore add yunshu0909/prd-doc-writer
```

## Metadata

- Status: approved
- Slug: yunshu0909-prd-doc-writer
- Skillstore revision: r1
- Version status: missing
- Tree hash: f185a64380a3787dfaf64a3e4898312a10d17b235c653abbaeca0841384023d9
- Author: yunshu0909
- GitHub username: yunshu0909
- License: MIT
- Repository: https://github.com/yunshu0909/yunshu\_skillshub/tree/master/prd-doc-writer
- Ref: 64ca8af0f54a325752f08bd54e52151061ea659a
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 80
- Quality tier: silver
- Public page: https://skillstore.pages.dev/skills/yunshu0909-prd-doc-writer
- Manifest: https://skillstore.pages.dev/api/skills/yunshu0909-prd-doc-writer/manifest

## Capabilities

- Builds a confirmed user journey map before drafting the full PRD.
- Guides each user story through focused questions and single-point confirmation.
- Requires ASCII wireframes for stories that include user interface decisions.
- Adds Mermaid flow, state, or sequence diagrams for product behavior alignment.
- Generates a final PRD using the included structured template.
- Can prepare a PRD registry row for project documentation tracking.

## Use Cases

- Define a New Product Feature: Turn an early feature idea into a staged PRD with stories, rules, edge cases, and acceptance criteria.
- Clarify UI Requirements: Align a team on page structure and user-visible behavior through ASCII wireframes and Mermaid diagrams.
- Prepare Development Handoff: Convert confirmed requirements into a developer-ready document with clear scope, non-goals, and testable outcomes.

## Prompt Templates

### Start a PRD

```
Help me create a PRD for [feature]. Start by asking questions, then build a journey map before drafting anything.
```

### Detail User Stories

```
Use this journey map: [paste map]. Walk through each stage and help me define user stories, business rules, and acceptance criteria.
```

### Add Visual Alignment

```
For this UI story, create an ASCII wireframe and a Mermaid flow diagram. Ask for confirmation before moving to acceptance criteria.
```

### Finalize and Register

```
Review our confirmed stories, surface missing decisions, then generate the final PRD. Also prepare a PRD registry row for version [version].
```

## Limitations

- It depends on user-provided product facts and should not invent missing requirements.
- It does not replace stakeholder approval, legal review, or engineering estimation.
- The diagrams are text drafts and may need design or architecture refinement.
- Registry updates need confirmed version IDs and repository paths from the user.

## Best Practices

- Provide real user roles, goals, business rules, and known constraints before final generation.
- Confirm each journey stage and user story before asking for the complete PRD.
- Use diagrams for flows with branches, states, timing, or user-visible failure handling.

## Anti Patterns

- Do not ask for a final PRD before the journey map and stories are confirmed.
- Do not use it to invent product decisions that stakeholders have not approved.
- Do not treat ASCII wireframes as final visual design specifications.

## Security Audit

- Audited at: 2026-07-08T10:51:58.829\+00:00
- Summary: Reviewed the flagged Markdown references, Mermaid diagrams, and multilingual PRD prose. All static findings are false positives from Markdown syntax, diagram examples, and entropy heuristics; no prompt injection or malicious intent was found.

## Stats

- Views: 164
- Downloads: 102
- Favorites: 2
- Popularity score: 0