agentleFS
Sign inStart free
wachawowachawo/claude-skills/skills/to-prd/SKILL.md

to-prd

Skill0 starsChanged 6 months agoMITView on GitHub

Turns the current conversation context into a PRD and publishes it to the project's issue tracker. Use when the user wants to create a PRD from the current context.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 124 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Write the PRD using the template below, then publish it to the project's issue tracker.

    line 20
  2. Distinctive:

    Do NOT include concrete file paths or code snippets.

    line 56
  3. Distinctive:

    Test precedents (i.e., similar kinds of tests in the codebase)

    line 64

“Common” is measured: kept by at least 6 in 10 of the 124 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

This skill takes the current conversation context and codebase understanding and produces a PRD. Do NOT interview the user — just synthesize what you already know.

The issue tracker and triage label vocabulary should have already been provided to you — if not, run /setup-matt-pocock-skills.

Process

  1. Explore the repository to understand the current state of the codebase, if you have not done so already. Use the project's domain glossary throughout the PRD and respect any ADRs in the area you are touching.
  2. Sketch the main modules you will need to build or modify to complete the implementation. Actively look for opportunities to factor out deep modules that can be tested in isolation.

A deep module (as opposed to a shallow one) encapsulates a lot of functionality behind a simple, testable interface that rarely changes.

Confirm with the user whether these modules match their expectations. Confirm which modules they want tests written for.

  1. Write the PRD using the template below, then publish it to the project's issue tracker. Apply the needs-triage label so it enters the standard triage flow.
<prd-template>

Problem Statement

The problem the user faces, from the user's perspective.

Solution

The solution to the problem from the user's perspective.

User Stories

A LONG numbered list of user stories. Each story should be in the format:

  1. As an <actor>, I want a <feature>, so that <benefit>
<user-story-example> 1. As a mobile bank customer, I want to see balance on my accounts, so that I can make better informed decisions about my spending </user-story-example>

This list of user stories should be very extensive and cover every aspect of the functionality.

Implementation Decisions

A list of accepted implementation decisions. This may include:

  • Modules that will be built/modified
  • Interfaces of those modules that will be changed
  • Technical clarifications from the developer
  • Architectural decisions
  • Schema changes
  • API contracts
  • Specific interactions

Do NOT include concrete file paths or code snippets. They can become stale very quickly.

Testing Decisions

A list of accepted testing decisions. Include:

  • A description of what makes a good test (test only external behavior, not implementation details)
  • Which modules will be tested
  • Test precedents (i.e., similar kinds of tests in the codebase)

Out of Scope

A description of things that are outside the scope of this PRD.

Further Notes

Any additional notes about the functionality.

</prd-template>

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.

Reviews can't be read right now.

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