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.

referencesprd-template.md

≈478 tokens on demand. Your agent reads this file only when SKILL.md points to it.

PRD template

Copy this into prds/<slug>.md. Delete sections that do not apply. Keep it under two screens.

# <Feature or problem, sentence case>

Created: YYYY-MM-DD HH:mm UTC
Last Updated: YYYY-MM-DD HH:mm UTC
Status: Draft

## Problem

One paragraph. Who hits it, what happens, why it matters now.

## Root cause

Bugs only. The specific line, query, or design decision that produces the problem. If unknown, say so and list the two most likely candidates.

## Proposed solution

What changes and why this approach over the alternatives. Two or three sentences per major decision.

## Files to change

- `path/to/file.ts` what changes here
- `path/to/other.tsx` what changes here
- new: `path/to/new.ts` what it does

## Edge cases

- Empty state
- Concurrent writes
- Auth missing or expired
- Existing data that does not match the new shape

## Verification steps

Commands or clicks that prove it works. Each one has an expected result.

1. `npx convex dev` runs clean, no schema errors
2. `npm run typecheck` passes
3. Open /page, do X, see Y
4. Dashboard shows no OCC retries on `mutationName` after 5 minutes of use

## Out of scope

Things that came up and were deliberately not done. Link an issue or a new PRD if they should happen later.

## Task completion log

- YYYY-MM-DD HH:mm UTC Started. Triage notes.
- YYYY-MM-DD HH:mm UTC Schema and mutation done. Verified step 1 and 2.
- YYYY-MM-DD HH:mm UTC UI wired. Verified step 3. Status: Done.

Notes on filling it in

  • Problem before solution. If the problem section is thin, the solution is a guess.
  • Files to change is the scope contract. If a file is not listed and needs to change, update the PRD first.
  • Verification steps are what moves a task to Completed. Write them so someone else could run them.
  • Out of scope is where feature creep goes to wait.
  • The completion log is append only. Do not rewrite history.

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