prd-writing
Write structured, opinionated PRDs that engineers actually read. Use when asked to write a PRD, product spec, feature requirements, or product requirements document. Creates concise, evidence-backed specs with clear scope boundaries and measurable success criteria.
What this skill does
Write PRDs that are evidence-first, concise, and scannable. A PRD is a thinking tool — if it's longer than 1200 words, the author hasn't thought hard enough. Brief specs are more likely to be read, more likely to be followed, and more likely to ship on time. ## Structure Follow this structure. Every section is mandatory unless marked optional. ### 1. Problem Lead with customer evidence. Quotes, data, support tickets, observed behavior. If you have no evidence, say so explicitly — that's an opinion-driven PRD and should be flagged. Example: > "3 of 5 interviewed customers abandon onboarding at the team invite step. Average time spent: 47 seconds before closing the tab." NOT: "Users find onboarding confusing." ### 2. Goals Measurable outcomes, not outputs. Each goal has a number attached. - "Reduce onboarding drop-off from 60% to under 30%" - NOT "Improve the onboarding experience" ### 3. Target Users Who specifically benefits. Be narrow. "Series A startup founders doing PM work before their first PM hire" — not "product managers." ### 4. Requirements Use P0/P1/P2 with clear definitions: - **P0** — Does not ship without it. The feature is broken or useless without this. - **P1** — Ships without it, but significantly degraded. Do in same cycle if possible. - **P2** — Nice to have. Candidate for fast follow. Each requirement is one sentence. If a requirement needs a paragraph to explain, it's too big — break it down. ### 5. Success Metrics Numbers. Always numbers. "Reduce X from Y to Z within W weeks." ALWAYS pair each metric with a counter-metric to prevent gaming: - Metric: "Increase activation rate to 70%" - Counter-metric: "Without decreasing 30-day retention below 45%" ### 6. Out of Scope What you are deliberately NOT building and why. This section prevents scope creep and signals that you've thought about boundaries. ### 7. Open Questions (optional) Unresolved decisions that need input. Each question names who should answer it and by when. ## Guidelines - CRITICAL: 800-1200 words maximum. Longer PRDs mean the thinking isn't done. - NEVER start from a solution. Start from a problem with evidence. - NEVER include implementation details — architecture, APIs, database schemas. That's spec territory, not PRD territory. - ALWAYS include Out of Scope. A PRD without boundaries invites scope creep. - ALWAYS trace requirements to customer evidence. No evidence = opinion. - NEVER use weasel metrics: "improve performance," "enhance experience," "increase engagement." Put a number on it or don't include it. - P0 requirements should number 3-5. If you have more than 5 P0s, you haven't prioritized. ## Example: Good vs Bad **Bad P0 requirement:** > "The system should handle authentication in a secure and user-friendly manner, supporting multiple providers and edge cases." **Good P0 requirement:** > "P0: User can sign up and log in with email + password. Google OAuth is P1." One sentence. Clear scope. Priority forces a decision. --- *Built on Linear's "short specs > exhaustive docs" philosophy. Skills from [productskills](https://github.com/assimovt/productskills).*
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.