Index of every page on this site: llms.txt
All skills
waynesutton avatar

/create-prd

@853b196
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/waynesutton/builder-skills/create-prd

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈105 tokens for metadata: the name and description. ≈614 when used: this file. ≈501 more on demand in 2 files.

Description uses 5.2% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈419 characters, or 5.2%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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. The required parts:

# <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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts11d3 checks · Risk SAFE
  • Gen Agent Trust Hub11d

    This skill provides a structured process for creating Project Requirements Documents (PRDs) and managing development tasks. It is safe to use and adheres to standard development planning workflows.

  • Socket11d

    No alerts

  • Snyk11d

    Risk: LOW · No issues

Signed by skilld at 853b196. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 6 days ago.

Activeupdated 2 weeks ago

README badge

README badge for waynesutton/builder-skills/create-prd