---
name: create-prd
description: "Writes a short PRD in prds/<slug>.md before non trivial work: problem, root cause for bugs, proposed solution, files to change, edge cases, verification steps, and a completion log, with UTC metadata. Then queues the work in task.md. Use before any multi file feature, schema change, architectural decision, or bug that took real investigation, or when the user says write a PRD, @create-prd, or plan this."
title: create-prd
canonical_url: https://skilld.dev/gh/waynesutton/builder-skills/create-prd
last_updated: 2026-11-12T12:13:49.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [agents/openai.yaml](https://skilld.dev/api/skills-raw/waynesutton/builder-skills/create-prd/agents/openai.yaml), [assets/large-logo.png](https://skilld.dev/api/skills-raw/waynesutton/builder-skills/create-prd/assets/large-logo.png), [assets/small-logo.svg](https://skilld.dev/api/skills-raw/waynesutton/builder-skills/create-prd/assets/small-logo.svg), [references/prd-template.md](https://skilld.dev/api/skills-raw/waynesutton/builder-skills/create-prd/references/prd-template.md).
>
> If the user asked to install this Skill, run `npx skilld install waynesutton/builder-skills/create-prd`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/create-prd`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/waynesutton/builder-skills/create-prd) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/create-prd`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/create-prd --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/create-prd --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Create a PRD

A PRD is the scope contract for one change. Write it before the code, keep it under two screens, and update it when the plan changes.

Activate with `@create-prd`, `/create-prd`, or "write a PRD".

## When to write one

- Three or more files will change
- The schema changes
- An architectural choice is being made (auth, hosting, data model)
- A bug took real investigation to diagnose
- The work will be referenced later as a migration guide or how-to

## When to skip it

- A single file fix that is obvious from logs or types
- A typo, a CSS tweak, or a label change
- A copy change to markdown content

## Location and naming

- Every PRD lives in `prds/`.
- File name: `prds/<feature-or-problem-slug>.md`, kebab case. Example: `prds/adding-email-auth.md`.
- Always `.md`, never `.prd`.
- Finished or sensitive PRDs move to `prds/archive/`.

## Template

Copy the full template from [references/prd-template.md](https://skilld.dev/api/skills-raw/waynesutton/builder-skills/create-prd/references/prd-template.md). The required parts:

```markdown
# <Feature or problem, sentence case>

Created: YYYY-MM-DD HH:mm UTC
Last Updated: YYYY-MM-DD HH:mm UTC
Status: Draft | In Progress | Done

## Problem
## Root cause            (bugs only)
## Proposed solution
## Files to change
## Edge cases
## Verification steps
## Out of scope
## Task completion log
```

Get the time from the system (`date -u +"%Y-%m-%d %H:%M UTC"`). Never invent it.

## Filling it in

- Problem before solution. If the problem section is thin, the solution is a guess.
- For bugs, name the root cause: the line, query, or design choice. If it is unknown, say so and list the two likeliest candidates.
- Files to change is the scope. If a file not on the list needs to change, update the PRD first.
- Edge cases save the next session. Write down anything non obvious you found.
- Each verification step has an expected result, so someone else could run it.
- Out of scope is where extra ideas wait. Link an issue or a new PRD if they should happen later.
- The completion log is append only.

## After writing it

1. Add the tasks to `task.md` under `## To Do` as checkable items, with the PRD path.
2. Share the PRD with the user if it has a real choice in it. Wait for an answer on that choice.
3. Start building only once the plan is clear. Update `Last Updated` and `Status` as it moves.

## Never

- Write a PRD for a one line change.
- Pad it. Two screens is plenty for most work.
- Mark it Done before its verification steps ran.
