Skip to content
Skill

natprd

by anatasof

AI Summary

An interactive, guided PRD generation skill for writing production-grade PRDs. Produces fully structured PRDs with user stories, Gherkin acceptance criteria, section-level rules, and optional sections — all in markdown format.

Install

Copy this and paste it into Claude Code, Cursor, or any AI assistant:

I want to install the "natprd" skill in my project.

Please run this command in my terminal:
# Install skill into your project
mkdir -p .claude/skills/NatPRD && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/NatPRD/SKILL.md "https://raw.githubusercontent.com/anatasof/NatPRD/main/SKILL.md"

Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.

Description

Activate this skill when the user wants to create, update, validate, or review a Product Requirement Document. Triggers on mentions of PRD, product requirements, user stories, acceptance criteria, or initiative documentation, or when the user describes a feature and asks for structured documentation.

PRD Maker

An interactive, guided PRD generation skill for writing production-grade PRDs. Produces fully structured PRDs with user stories, Gherkin acceptance criteria, section-level rules, and optional sections — all in markdown format. ---

What This Skill Does

When activated, this skill: • Interviews the user section by section using focused questions • Validates each answer against the section rules before moving on • Writes the PRD incrementally, showing each section as it's completed • Enforces the PRD standard — no placeholders, no rule violations allowed • Outputs a complete prd.md file (default location: docs/prd.md) The 12 core sections, 4 optional sections, scoring rubric, and per-section rules live in the supporting files referenced at the bottom of this document. Load them on demand when you need the full text — do not duplicate them here. ---

How to Activate

Simply say: • "I want a PRD for [feature/initiative name]" • "Help me write a PRD" • "Create a PRD for [description]" • "Review my PRD" — to validate an existing PRD file Claude will detect the intent and load this skill automatically. In Claude Code it can also be invoked directly with /natprd. ---

User-Choice Presentation

Whenever an interview question offers a choice between 2–4 discrete, mutually-exclusive options, present it using the AskUserQuestion tool so the user can click rather than type. This applies across all three modes. The tool caps at 4 listed options and automatically adds an "Other" escape, so you can cover up to 5 outcomes (4 explicit + Other) without listing them all. Examples that MUST use buttons: • §2 Document Status — list the 4 most common (Draft / In Review / Approved / In Execution); "Other" covers Deprecated • §6 Hypothesis confidence (High / Medium / Low) • §8 MoSCoW priority (Must-have / Should-have / Could-have / Won't-have) • §7 Metric type (Leading / Lagging / Guardrail) • Any yes/no compliance flag in §0.3 • "Any more user stories?" (Yes — add another / No — move on) • A diagram offer at §8, §9, or §11 (Yes, add it / No, skip) Exceptions — keep as plain text: • Open-ended questions (the working name in §0.1, evidence narrative in §3, hypothesis prose in §6, baseline/target values in §7): no discrete option set. • Questions with >5 effective options (e.g., §0.2 initiative type with 8 options): keep as text, or split into two sequential button questions. • Multi-select (e.g., §0.3 compliance signals — multiple may apply): use AskUserQuestion with multiSelect: true, up to 4 grouped categories. If a question doesn't naturally fit any of these patterns, default to text — never invent options to force a button UI. ---

Discussion

0/2000
Loading comments...

Health Signals

MaintenanceCommitted 5mo ago
◐ Stale
AdoptionUnder 100 stars
53 ★ · Niche
DocsREADME + description
Well-documented

GitHub Signals

Stars53
Forks9
Issues0
Updated5mo ago
View on GitHub
BSD-3-Clause License

My Fox Den

Community Rating

Sign in to rate this booster

Works With

Claude Code