What are P0, P1, and P2 requirements?

P0 are 'must-haves' required to ship; P1 are important features that can follow shortly after; P2 are 'nice-to-have' items for future cycles.

How does the skill handle metrics?

It requires specific numerical goals and pairs every metric with a counter-metric to ensure that improving one area doesn't negatively impact another.

Why is there a 1200-word limit?

Brief specs are more likely to be read and followed; the limit ensures the author has distilled the most important product thinking before reaching the engineering phase.

Can I include technical implementation details in these PRDs?

No, the skill intentionally excludes architecture, APIs, and database schemas to keep the focus on user problems and requirements rather than implementation.

What makes this PRD skill different from general writing?

It enforces an 'opinionated' structure based on evidence, strictly limits word count for readability, and mandates measurable counter-metrics to prevent gaming the system.

Professional PRD Writing

Name: Professional PRD Writing
Author: assimovt

byassimovt

•

협업 도구

Generates concise, evidence-driven Product Requirements Documents (PRDs) that bridge the gap between product vision and engineering execution.

This skill transforms Claude into a disciplined product manager, producing opinionated and structured PRDs that engineers actually read. Based on high-growth product philosophies like Linear's, it enforces a strict 1200-word limit to ensure clarity and density of thought. The skill requires evidence-first problem statements, measurable goals with counter-metrics, and explicit P0/P1/P2 prioritization. By focusing on customer behavior data rather than subjective opinions, it ensures that product requirements are actionable, scoped correctly, and centered on user outcomes rather than just features.

주요 기능

01Evidence-first problem identification using customer data and quotes

02Separation of product requirements from technical implementation details

0328 GitHub stars

04Automatic enforcement of brevity with an 800-1200 word maximum

05Measurable success metrics paired with counter-metrics to prevent gaming

06Strict P0/P1/P2 prioritization with clear scope boundaries

사용 사례

01Defining clear project boundaries and success criteria for a new feature launch

02Facilitating alignment between product and engineering through scannable documentation

03Converting customer interview notes and raw data into a formal product specification

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add assimovt/productskills prd-writing

For use in Claude.ai and ChatGPT

Download Skill