agentleFS
Sign inStart free
Thirumalai-Tech-DeveloperThirumalai-Tech-Developer/Kratos_Agent/skills/to-prd/SKILL.md

to-prd

Skill1 starsChanged 48 days agoMITView on GitHub

Turn an idea or request into a concise product requirements document with outcomes, users, scope, constraints, and acceptance criteria.

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 8 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

  • +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:

    Use when the user asks for a PRD, product brief, or requirements document.

    line 9
  2. Distinctive:

    Write only the sections the request needs: problem, users, goals, non-goals, user-visible behavior, requirements, constraints, risks, and …

    line 13
  3. Distinctive:

    Keep requirements testable and distinguish required behavior from proposed implementation.

    line 14
  4. Very specific:

    Do not invent business rules or add scope to make the document look complete.

    line 17

“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

Write a PRD

Use when the user asks for a PRD, product brief, or requirements document.

  1. Preserve the user's stated problem, audience, outcome, and constraints. Mark assumptions instead of presenting them as facts.
  2. Inspect the existing project when available; note relevant architecture or behavior that affects the requirements.
  3. Write only the sections the request needs: problem, users, goals, non-goals, user-visible behavior, requirements, constraints, risks, and observable acceptance criteria.
  4. Keep requirements testable and distinguish required behavior from proposed implementation.
  5. Save a file only when requested or when the task already calls for a project artifact. Otherwise return the PRD in the conversation.

Do not invent business rules or add scope to make the document look complete. This Kratos skill retains the requested to-prd name; the current upstream Matt Pocock skill uses to-spec.

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