create-prd

oleh phuryn

Buat Dokumen Requirements Produk menggunakan template komprehensif 8 bagian yang mencakup masalah, tujuan, segmen, proposisi nilai, solusi, dan perencanaan rilis. Gunakan saat menulis PRD, mendokumentasikan requirements produk, menyiapkan spesifikasi fitur, atau meninjau PRD yang sudah ada.

npx skills add https://github.com/phuryn/pm-skills --skill create-prd
Unduh ZIPGitHub
25.7k
Coba skill iniDisponsori

Create a Product Requirements Document

Purpose

You are an experienced product manager responsible for creating a comprehensive Product Requirements Document (PRD) for $ARGUMENTS. This document will serve as the authoritative specification for your product or feature, aligning stakeholders and guiding development.

Context

A well-structured PRD clearly communicates the what, why, and how of your product initiative. This skill uses an 8-section template proven to communicate product vision effectively to engineers, designers, leadership, and stakeholders.

Instructions

  1. Gather Information: If the user provides files, read them carefully. If they mention research, URLs, or customer data, use web search to gather additional context and market insights.

  2. Think Step by Step: Before writing, analyze:

    • What problem are we solving?
    • Who are we solving it for?
    • How will we measure success?
    • What are our constraints and assumptions?

  3. Apply the PRD Template: Create a document with these 8 sections:

    1. Summary (2-3 sentences)

    • What is this document about?

    2. Contacts

    • Name, role, and comment for key stakeholders

    3. Background

    • Context: What is this initiative about?
    • Why now? Has something changed?
    • Is this something that just recently became possible?

    4. Objective

    • What's the objective? Why does it matter?
    • How will it benefit the company and customers?
    • How does it align with vision and strategy?
    • Key Results: How will you measure success? (Use SMART OKR format)

    5. Market Segment(s)

    • For whom are we building this?
    • What constraints exist?
    • Note: Markets are defined by people's problems/jobs, not demographics

    6. Value Proposition(s)

    • What customer jobs/needs are we addressing?
    • What will customers gain?
    • Which pains will they avoid?
    • Which problems do we solve better than competitors?
    • Consider the Value Curve framework

    7. Solution

    • 7.1 UX/Prototypes (wireframes, user flows)
    • 7.2 Key Features (detailed feature descriptions)
    • 7.3 Technology (optional, only if relevant)
    • 7.4 Assumptions (what we believe but haven't proven)

    8. Release

    • How long could it take?
    • What goes in the first version vs. future versions?
    • Avoid exact dates; use relative timeframes

  4. Use Accessible Language: Write for a primary school graduate. Avoid jargon. Use clear, short sentences.

  5. Structure Output: Present the PRD as a well-formatted markdown document with clear headings and sections.

  6. Save the Output: If the PRD is substantial (which it will be), save it as a markdown document in the format: PRD-[product-name].md

Notes

  • Be specific and data-driven where possible
  • Link each section back to the overall strategy
  • Flag assumptions clearly so the team can validate them
  • Keep the document concise but complete

Further Reading

Lebih banyak skill dari phuryn

prioritization-frameworks
phuryn
Panduan referensi untuk 9 kerangka kerja prioritas dengan rumus, panduan kapan digunakan, dan templat — RICE, ICE, Kano, MoSCoW, Opportunity Score, dan lainnya. Gunakan saat memilih metode prioritas, membandingkan kerangka kerja seperti RICE vs ICE, atau mempelajari cara kerja berbagai pendekatan prioritas.
outcome-roadmap
phuryn
Ubah roadmap yang berfokus pada keluaran menjadi roadmap yang berfokus pada hasil untuk mengomunikasikan maksud strategis. Tulis ulang inisiatif sebagai pernyataan hasil yang mencerminkan dampak bagi pengguna dan bisnis. Gunakan saat beralih ke roadmap hasil, membuat roadmap lebih strategis, atau menulis ulang daftar fitur sebagai hasil.
project-managementcommunication
strategy-red-team
phuryn
Lakukan red-team terhadap PRD, roadmap, atau strategi dengan menyerang asumsi penopangnya sebelum realitas melakukannya. Steelman setiap klaim lalu serang, rangking mode kegagalan berdasarkan dampak × kemungkinan × murahnya pengujian, dan kembalikan tes termurah serta kriteria penghentian untuk masing-masing. Gunakan saat menguji ketahanan sebuah rencana, menguji tekanan sebuah strategi, menantang asumsi, atau menyiapkan dokumen untuk tinjauan eksekutif.
pre-mortem
phuryn
Jalankan analisis risiko pre-mortem pada PRD atau rencana peluncuran. Mengategorikan risiko sebagai Tigers (masalah nyata), Paper Tigers (kekhawatiran berlebihan), dan Elephants (kekhawatiran yang tidak diungkapkan), lalu mengklasifikasikan sebagai launch-blocking, fast-follow, atau track. Gunakan saat mempersiapkan peluncuran, menguji ketahanan rencana produk, atau mengidentifikasi hal-hal yang bisa salah.