agentleFS
teja1103teja1103/Claude-Skills/skills/prd-writer/SKILL.md

prd-writer

Skill0 starsChanged 8 months agoNo licenceView on GitHub

Turns raw, unstructured requirement points (bullet lists, meeting notes, Slack dumps, voice-to-text braindumps) into a polished, well-structured Product Requirements Document. Asks the user which document format/template to use before drafting, and automatically builds a role-policy (permissions) matrix whenever the requirements mention distinct roles, actors, or access levels. Use when the user says "turn these into a PRD", "write a PRD from these notes", "draft a product requirements document", "structure these requirements", or pastes raw feature/requirement bullets and asks for a formal spec. Do not use for pure technical design docs/RFCs with no product framing, for generic documentation writing unrelated to requirements, or for summarizing meeting notes without turning them into a requirements artifact.

39 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use experiment-designer, user-research and 1 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.
  • Dokkabei97Skill

    experiment-designer

    Designs A/B tests and product experiments with hypothesis structuring, sample size calculation, duration estimation, and result interpretation. Unified framework for both product and marketing experiments.

    Also in 3 projects that use this

  • AnthropicSkill

    user-research

    Plan, conduct, and synthesize user research. Trigger with "user research plan", "interview guide", "usability test", "survey design", "research questions", or when the user needs help with any aspect of understanding their users through research.

    Also in 3 projects that use this

  • OpenAISkill

    brainstorming

    You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 28 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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.