agentsclimarketplace

Create prd

Skill lhenrique42/ai-templates/skills/create-prd

Templates for agents, skills, prompts and instructions

Install
npx -y skills add lhenrique42/ai-templates --skill create-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

  • 0 stars0 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.

What its author says it does

Copied from the file, not written here

Create Product Requirements Documents (PRDs) from feature requests using a structured clarification, planning, and drafting workflow. Use when asked to create a PRD, define requirements, or document a new feature. Do not use for technical specifications, task breakdowns, or implementation planning.

SKILL.md

3.2 KB, as published. Nobody here has run it

Create PRD

Outcome

Create one standardized PRD markdown file in the project's tasks directory.

When to Use

  • User asks to create a PRD
  • User asks to define requirements for a feature
  • User asks to document a new feature in product terms

Do Not Use

  • Technical design or architecture specifications
  • Engineering task breakdowns or sprint plans
  • Implementation sequencing or low-level solution design

Inputs

  • Feature request or problem statement
  • Optional business context, constraints, timelines, and stakeholders

Workflow

1) Clarify the Request

Extract the core requirement set before drafting.

Capture:

  • Problem statement
  • Target users
  • Desired business or user outcome
  • Constraints (timeline, compliance, platform, budget)
  • Known assumptions

If critical information is missing, ask focused questions before drafting.

Decision points:

  • If user/persona is unclear, ask who the feature serves.
  • If success is undefined, ask for measurable outcomes.
  • If request is ambiguous, restate understanding and ask for confirmation.

2) Plan the PRD Scope

Define boundaries and requirement intent.

Plan:

  • In-scope capabilities
  • Out-of-scope boundaries
  • Functional requirements
  • Non-functional requirements (reliability, privacy, performance, compliance)
  • Dependencies and constraints
  • Risks and open questions

Branching logic:

  • If request is too broad, split into MVP and later phases.
  • If regulated/sensitive data is involved, expand compliance/privacy requirements.
  • If legacy systems are involved, add migration or compatibility constraints.

3) Draft the PRD

  1. Locate the project tasks directory using this priority:
    • Existing tasks/
    • Existing project-tasks/
    • Existing docs/tasks/
    • Existing .github/tasks/
    • If none exist, create tasks/
  2. Create file name: YYYY-MM-DD-prd-<feature-slug>.md
  3. Draft the PRD using PRD template
  4. Fill all sections with concise, testable requirement language.

Drafting rules:

  • Write product requirements, not implementation details.
  • Use explicit SHALL-style language for hard requirements when helpful.
  • Mark unknowns as TBD and add them to open questions.

4) Quality Check Before Finalizing

Validate the document before returning it.

Completion checks:

  • Clear problem statement and user value
  • Explicit in-scope and out-of-scope sections
  • Measurable success metrics
  • Functional and non-functional requirements included
  • Dependencies, risks, and open questions documented
  • No technical spec or task decomposition content

5) Return Result

Provide:

  • Created file path
  • One-paragraph summary of the PRD
  • Any unresolved questions needing user input

Output Contract

The generated PRD should be a single markdown file in the tasks directory and follow the template sections in PRD template.

Keep looking

Skills are one crate of 328,083. 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.