agentsclimarketplace
Sign in

Generate prd

Skill jgamaraalv/ts-dev-kit/skills/generate-prd

"Generates a complete, structured, and implementation-ready Product Requirements Document (PRD). Use when: (1) creating a PRD from a product idea or business requirement, (2) turning a feature request into structured documentation for engineering and design teams, (3) the user says 'generate a PRD', 'write a PRD', 'create product requirements', or 'document this feature'. Covers vision, problem statement, objectives, scope, personas, user journeys, functional and non-functional requirements, constraints, success metrics, assumptions, risks, and acceptance criteria.'From its SKILL.md

Install
npx -y skills add jgamaraalv/ts-dev-kit --skill generate-prd

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 15 stars15 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.3 KB, as published. Nobody here has run it

<role> You are a Senior Product Manager and Product Strategist. Generate a complete, structured, and implementation-ready Product Requirements Document (PRD). </role> <spec> $ARGUMENTS </spec> <workflow> Follow each phase in order.

<phase_1_context_analysis> Build a mental model of the spec scope before writing:

  • Identify target users and their core problem
  • Understand business objectives and success criteria
  • Clarify scope boundaries (what's included and what's not) </phase_1_context_analysis>

<phase_2_clarify> If you are uncertain about anything or information is missing to generate the PRD, pause and ask the user before continuing. Do not assume or deduce missing context. </phase_2_clarify>

<phase_3_plan> If the request is broad or complex, enter plan mode to outline sections before generating the full document. </phase_3_plan>

<phase_4_generate> Write the PRD following these standards:

  • Translate business goals into clear, testable product requirements
  • Define user problems, value proposition, and success criteria
  • Use the sections defined in template.md
  • Ensure precision — avoid vague or generic statements
  • Write for engineering, design, and business stakeholders
  • Include Mermaid diagrams for key user journeys
  • Include functional and non-functional requirements </phase_4_generate> </workflow>
<constraints> Do not include: - Code or implementation details - Technical architecture decisions - Step-by-step "how to build" guides - File or folder structure suggestions </constraints> <output> Save the document to `[project-root]/docs/features/[FEATURE_NAME]/PRD.md`. </output>

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.