agentleFS
Sign inStart free
waynesuttonwaynesutton/markdown-site/.cursor/skills/create-prd/SKILL.md

create-prd

Skill628 starsChanged 7 months agoMITView on GitHub

Use this skill before any multi-file feature, architectural decision, or complex bug fix. Activate with: @create-prd Copy and fill in this template:

44 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use prioritize-features, brainstorm-okrs and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • skytiger6724Skill

    prioritize-features

    Prioritize a backlog of feature ideas based on impact, effort, risk, and strategic alignment with top 5 recommendations. Use when prioritizing a feature backlog, making scope decisions, or ranking product ideas.

    Also in 4 projects that use this

  • skytiger6724Skill

    brainstorm-okrs

    Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.

    Also in 4 projects that use this

  • miovragSkill

    strategy-red-team

    Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.

    Also in 3 projects that use this

  • launchapp-devSkill

    interview-script

    Create a structured user interview script with warm-up, core exploration, and wrap-up sections. Use when preparing for user research interviews to ensure consistent, insightful conversations.

    Also in 4 projects that use this

  • About-IntelligenceSkill

    beachhead-segment

    Identify the first beachhead market segment for a product launch.

    Also in 4 projects that use this

  • nandanosqlSkill

    customer-journey-map

    Map the complete customer experience across all touchpoints using the NNGroup framework. Identifies pain points, emotions, and opportunities at every stage of the user journey.

    Also in 5 projects that use this

  • +5 more from skytiger6724

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 42 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill before any multi-file feature, architectural decision, or complex bug fix.

    line 3
  2. Very specific:

    All PRDs live in prds/ folder

    line 9
  3. Very specific:

    Use kebab-case for the filename (e.g., prds/adding-email-auth.md)

    line 12
  4. Very specific:

    Add the feature tasks to TASK.md under ## To Do as checkable items

    line 74

“Common” is measured: kept by at least 6 in 10 of the 42 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Create a PRD

Use this skill before any multi-file feature, architectural decision, or complex bug fix.

Activate with: @create-prd

Location and naming

  • All PRDs live in prds/ folder
  • File name: prds/<feature-or-problem-slug>.md
  • Extension is always .md, not .prd
  • Use kebab-case for the filename (e.g., prds/adding-email-auth.md)

Template

Copy and fill in this template:

# [Feature or problem name]

## Summary

1-2 sentence description of what this is and why it matters.

## Problem

What is broken or missing. Include symptoms, error messages, or user-facing impact.

## Root cause (for bugs)

What actually caused it. Do not skip this for bugs.

## Proposed solution

How to fix or build it. Be specific about the approach chosen and why.

## Files to change

- `path/to/file.ts` - what changes and why
- `convex/schema.ts` - if schema changes are needed

## Edge cases and gotchas

Anything non-obvious that came up during analysis. This section saves the next session.

## Verification

How to confirm the fix or feature works:

- [ ] Step 1
- [ ] Step 2

## Related

Links to related PRDs, issues, or external docs if any.

When to create a PRD

  • 3+ files will change
  • Schema changes are involved
  • Architectural decisions are being made (auth, hosting, data model)
  • A bug required significant investigation to diagnose
  • A feature needs to be referenced later as a migration guide or implementation reference

When to skip a PRD

  • Single file bug fix obvious from logs or types
  • Typo, CSS tweak, or label change
  • Copy change to markdown content

After creating the PRD

  1. Add the feature tasks to TASK.md under ## To Do as checkable items
  2. Reference the PRD path in the TASK.md entry if useful
  3. Begin implementation only after the plan is clear

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free