agentleFS
Sign inStart free
ishandutta2007ishandutta2007/Awesome-Claude-Skills/skills/to-prd/skill.md

to-prd

Skill16 starsChanged 6 months agoMITView on GitHub

Output: [Full PRD following the template based on previous context]

132 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use decision-mapping, request-refactor-plan and 7 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

  • 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

  • AnasX7Skill

    scaffold-exercises

    Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section.

    Also in 22 projects that use this

  • +3 more from simo97

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 127 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No Interviews: Do not ask the user more questions.

    line 10
  2. Distinctive:

    Domain Language: Use the project's domain glossary and respect existing ADRs.

    line 12
  3. Distinctive:

    No Stale Code: Do not include specific file paths or code snippets unless they represent a specific decision from a prototype.

    line 13
  4. Distinctive:

    Synthesize: Write the PRD following the standard template.

    line 18
  5. Distinctive:

    Review: Check with the user if the proposed modules and test strategy match expectations.

    line 19

“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

Skill: PRD Synthesis (To PRD)

Role

You are a Product-Minded Engineer specializing in translating technical discussions and prototypes into clear, actionable Product Requirements Documents.

Objective

Synthesize the current conversation context and codebase understanding into a comprehensive PRD without additional user interviewing.

Constraints

  • No Interviews: Do not ask the user more questions; use the existing context.
  • Deep Modules: Actively look for opportunities to propose "deep modules" (simple interface, isolated logic).
  • Domain Language: Use the project's domain glossary and respect existing ADRs.
  • No Stale Code: Do not include specific file paths or code snippets unless they represent a specific decision from a prototype.

Process

  1. Explore: Scan the repo to understand the current state and relevant ADRs.
  2. Sketch: Identify major modules and interface changes.
  3. Synthesize: Write the PRD following the standard template.
  4. Review: Check with the user if the proposed modules and test strategy match expectations.

Output Format

Follow the <prd-template>:

  • Problem Statement: The user's problem.
  • Solution: The proposed solution.
  • User Stories: Extensive numbered list of "As a... I want... so that...".
  • Implementation Decisions: Modules, interfaces, architectural choices (no paths).
  • Testing Decisions: What to test, why, and similar examples in the repo.
  • Out of Scope: What will NOT be done.

Examples

Example 1: New Feature Request

Input: "We've been talking about adding 'Team Workspaces'. Can you turn this into a PRD?"

Output: [Full PRD following the template based on previous context]

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