agentleFS
Sign inStart free
flopperjflopperj/dotfiles-core/.claude/skills/to-prd/SKILL.md

to-prd

Skill3 starsChanged 10 days agoMITView on GitHub

Turn the current conversation context into a PRD and save it as a markdown file. Use when the user wants to capture a feature plan, design discussion, or implementation idea as a structured PRD. Triggers on "to-prd", "create a PRD", "write a PRD", "save this as a PRD".

132 other projects use a version of this, 92 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use decision-mapping, zoom-out 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.
  • FabienDehopreSkill

    decision-mapping

    Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.

    Also in 8 projects that use this

  • victorgarciaesgiSkill

    zoom-out

    Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.

    Also in 60 projects that use this

  • simo97Skill

    request-refactor-plan

    Use this skill when user wants to create a refactor plan.

    Also in 23 projects that use this

  • simo97Skill

    edit-article

    The user will invoke this skill to help them edit an article.

    Also in 23 projects that use this

  • kennethkeimSkill

    ubiquitous-language

    Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".

    Also in 23 projects that use this

  • AnasX7Skill

    setup-pre-commit

    Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.

    Also in 34 projects that use this

  • +4 more from simo97

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 127 edited versions we read keep these.

  • 3

    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. Distinctive:

    Ask the user to confirm or correct before continuing.

    line 24
  2. Very specific:

    Create the prds/ directory if it doesn't exist

    line 32
  3. Distinctive:

    Use the template below. Be thorough — especially on user stories.

    line 36
  4. Distinctive:

    After writing the file:

    line 40

“Common” is measured: kept by at least 6 in 10 of the 127 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 structured PRD saved as a markdown file. Do NOT interview the user — synthesize what you already know from the conversation.

Process

1. Explore the codebase (if not already done)

Explore the repo to understand the current state of any code relevant to this feature. Identify the major modules that would need to be built or modified.

Actively look for opportunities to extract deep modules — modules that encapsulate a lot of functionality behind a simple, stable, testable interface. Prefer deep modules over shallow ones.

2. Check understanding with the user

Before writing, present:

  • A short summary of the problem and proposed solution as you understand it
  • A list of the major modules you expect to build or modify
  • Which of those modules you'd recommend writing tests for

Ask the user to confirm or correct before continuing.

3. Resolve the output path

Output path: ~/.claude/tasks/<project>/prds/<slug>.md

  • Resolve <project> with: basename "$(git rev-parse --show-toplevel 2>/dev/null || pwd)"
  • Derive <slug> from the feature name: lowercase, words separated by hyphens (e.g., user-profile-caching.md)
  • Create the prds/ directory if it doesn't exist

4. Write the PRD

Use the template below. Be thorough — especially on user stories. A short PRD is a weak PRD.

5. Confirm and share

After writing the file:

  • Show the full resolved path
  • Print a short summary (problem + solution, 2–3 sentences)
  • Suggest the user share the file path with teammates or attach it to the relevant Jira ticket

PRD Template

# PRD: <Feature Name>

**Project:** <project>
**Date:** <YYYY-MM-DD>
**Status:** Draft

---

## Problem Statement

The problem that the user is facing, from the user's perspective.

---

## Solution

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

---

## User Stories

A numbered list of user stories covering all aspects of the feature. Each in the format:

1. As a <actor>, I want <feature>, so that <benefit>.

Be exhaustive — cover happy paths, edge cases, error states, and admin/operator scenarios.

---

## Implementation Decisions

A list of implementation decisions made during planning. May include:

- Modules to build or modify
- Interface contracts between modules
- Architectural decisions and trade-offs considered
- Schema changes
- API contracts
- Specific interactions and data flows

Do NOT include specific file paths or code snippets — they go stale fast.

---

## Testing Decisions

- What makes a good test for this feature (test external behavior, not implementation details)
- Which modules will have tests written
- Prior art in the codebase (similar test patterns to follow)

---

## Out of Scope

What is explicitly not being built in this iteration.

---

## Further Notes

Anything else worth capturing — open questions, follow-up spikes, links to prior art or related PRDs.

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