prd-generator SKILL.md skillA

prd-generator from nicepkg/ai-workflow is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add nicepkg/ai-workflow/prd-generator@git:20260118.be84779

Pins git:20260118.be84779 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: nicepkg/ai-workflow
Path: workflows/product-manager-workflow/.claude/skills/prd-generator/SKILL.md
Versions recorded: 1
Latest version: git:20260118.be84779, committed Jan 18, 2026
Size: 15,352 bytes
Repository stars: 291
License: MIT

Generate comprehensive Product Requirements Documents (PRDs) for product managers. Use this skill when users ask to "create a PRD", "write product requirements", "document a feature", or need help structuring product specifications.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# PRD Generator

## Overview

Generate comprehensive, well-structured Product Requirements Documents (PRDs) that follow industry best practices. This skill helps product managers create clear, actionable requirements documents that align stakeholders and guide development teams.

## Core Workflow

When a user requests to create a PRD (e.g., "create a PRD for a user authentication feature"), follow this workflow:

### Step 1: Gather Context

Before generating the PRD, collect essential information through a discovery conversation:

**Required Information:**
- **Feature/Product Name**: What are we building?
- **Problem Statement**: What problem does this solve?
- **Target Users**: Who is this for?
- **Business Goals**: What are we trying to achieve?
- **Success Metrics**: How will we measure success?
- **Timeline/Constraints**: Any deadlines or limitations?

**Discovery Questions to Ask:**

```
1. What problem are you trying to solve?
2. Who is the primary user/audience for this feature?
3. What are the key business objectives?
4. Are there any technical constraints we should be aware of?
5. What does success look like? How will you measure it?
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add nicepkg/ai-workflow/prd-generator@sha256:37024f403238962e

The line at the top of this page pins the label git:20260118.be84779, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

[![mdr](https://markdownregistry.com/badge/art_fwqlvxptcrhocb5u.svg)](https://markdownregistry.com/a/art_fwqlvxptcrhocb5u)

3 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 1 version of this file, committed on Jan 18, 2026.

version	committed	commit	size	audit
git:20260118.be84779 latest	2026-01-18	be84779	15,352 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (15352 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag

Source

GitHub

nicepkg/ai-workflow · 291 stars · license MIT · pushed 2026-01-20 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_fwqlvxptcrhocb5u
GET https://markdownregistry.com/api/v1/resolve?ref=nicepkg/ai-workflow/prd-generator
GET https://markdownregistry.com/api/v1/blob/37024f403238962eceed83399637945248e11c4a2597eb95e980301b7de05438

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from nicepkg/ai-workflow

add-new-skills-to-workflow SKILL.md skill

nicepkg/ai-workflow · .claude/skills/add-new-skills-to-workflow/SKILL.md · Add new skills to an existing workflow and update all related documentation. Use when user wants to add skills from…

git:20260120.0b3efef · audit A · 291 stars

legacy-to-ai-ready SKILL.md skill

nicepkg/ai-workflow · .claude/skills/legacy-to-ai-ready/SKILL.md · Transform legacy codebases into AI-ready projects with Claude Code configurations. Use when (1) analyzing old projects…