prd
/prd
Pisze PRD w katalogu docs/prd z metrykami, kryteriami akceptacji, granicami zakresu, ryzykami i blokerami dla dużych zmian.
- Autor
- jeffersonvalente ↗
- Repozytorium
- cardume ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 04.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 04.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Pisze PRD w katalogu docs/prd z metrykami, kryteriami akceptacji, granicami zakresu, ryzykami i blokerami dla dużych zmian.
Oryginalny opis (EN)
Writes a PRD in docs/prd/ with metrics, acceptance criteria, no-gos, risks and blockers. Use for level-3 work: a new system or product phase, or when the user asks for a PRD; feature-level work uses spec.
Jak działa
- Before writing
- Write docs/prd/<slug>.md (or docs/prd/PHASE-N.md for phased projects)
- Rules for criteria
- After
Podgląd SKILL.md
--- name: prd description: "Writes a PRD in docs/prd/ with metrics, acceptance criteria, no-gos, risks and blockers. Use for level-3 work: a new system or product phase, or when the user asks for a PRD; feature-level work uses spec." allowed-tools: Read Glob Grep Write Edit --- # PRD — Product requirements for a product or phase A PRD answers *what* and *why* for a whole product or phase, with acceptance criteria someone can check without asking the author. Features inside it get their own spec later (`spec` skill). ## Before writing 1. Read what exists: README, `docs/standards.md`, previous PRDs in `docs/prd/`, the last gate report in `docs/gates/` (the last approved gate tells which phase comes next), research notes. 2. Ask the user what you cannot infer (or, as a subagent, return the questions under **Open questions** and stop; the caller asks the user): who the users are, the outcome that makes this phase a success, hard constraints (deadline, budget, compliance, platforms), and what is explicitly out. In the main conversation, use the `AskUserQuestion` tool — multiple choice, the recommended option first, free text always available. Follow the `brainstorming` skill when the idea is still fuzzy. ## Write `docs/prd/<slug>.md` (or `docs/prd/PHASE-N.md` for phased projects) ```markdown # PRD — <Product or phase name> Status: draft | approved | implemented | superseded (by <link>) · Date: <YYYY-MM-DD> · Owner: <user> ## Problem and evidence <Who has which problem today and how we know: data, support tickets, interviews, observed behavior. If there is no evidence yet, say so — that is a value risk below.> ## Objective <One sentence: the outcome this delivers.> ## Success metrics | Metric | Baseline | Target | When measured | |--------|----------|--------|---------------| | <outcome, e.g. invoices paid within 30 days> | 61% | 75% | 60 days after release | ## Appetite <How much time/effort this phase is worth (e.g. "2 weeks, one developer"). When the work outgrows it, cut scope rather than extend the budget.> ## User stories - As a <user>, I want <capability> so that <benefit>. (justification: <link or reason>) ## Acceptance criteria | ID | Criterion | How to verify | Who verifies | |----|-----------|---------------|--------------| | C1 | <observable result with a number when it is about speed/size/quality> | <command, test, or written script step> | QA / user / automated | ## Out of scope - <explicitly not in this phase, and where it goes instead> ## Rabbit holes and no-gos - <tempting detail or edge case that would blow the appetite, and the decision taken to avoid it> ## Risks - [value | usability | feasibility | viability] <risk> — early warning sign: <concrete signal> — mitigation: <…> ## Human test script <Required when real users must validate the phase: step by step, what to observe, what to ask afterwards.> ## Blockers - <decisions only the user can make; the PRD stays draft while this list is not empty> ``` ## Rules for criteria - Every criterion is checkable by a command/test or by a written script someone can follow. Words like "intuitive", "fast", "works well" need a number or a test, or they are not criteria. - One behavior per criterion; IDs are stable so specs, tasks and gate reports can reference them. - A phase PRD does not pull in deliverables from the next phase — note them under Out of scope. - Success metrics are outcomes measured after release (adoption, conversion, time saved); acceptance criteria are what the gate checks before release. Keep them apart, because shipping every criterion does not prove the outcome happened. - Tag each risk with its type — value (will they want it), usability (can they use it), feasibility (can we build it), viability (does it work for the business: cost, legal, support) — so the riskiest kind gets tested first. ## After Show the user the criteria table, the out-of-scope list and the blockers, and ask for approval (or, as a subagent, return them under **Open questions**). When approved: set `Status: approved` (`verify` later sets `implemented`; a replaced PRD becomes `superseded`), record significant product/technical decisions with the `adr` skill, and hand the PRD to `software-architect`, which writes contracts, ADRs and the feature list in `docs/prd/<slug>-architecture.md`. Every feature then gets its own spec (`spec` skill; quick spec for small ones) — a PRD is never broken into tasks directly.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · jeffersonvalente/cardume | 100 | MIT |
| stefanoskarakasis/product-marketing-skills | 100 | MIT |
| duronext/jig | 100 | MIT |
| OpenHands/extensions | 100 | MIT |
| alienfast/claude | 100 | MIT |
| rafagomes/ai-workflow | 100 | MIT |
| nkhanhpham99/ai-pm-os | 100 | MIT |
| fakoli/anvil | 100 | MIT |
| omexit/claude-skills-pack | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 9073ca440099 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100prd-writing
Opisuje metodę pisania krótkiego PRD z problemem, metrykami, zakresem, historiami użytkownika z kryteriami akceptacji, przypadkami brzegowymi i kryteriami startu, bez narzucania implementacji. - 100v1-prd
Zamienia zgłoszenie, issue albo pomysł na funkcję w dokument PRD z wymaganiami i kryteriami akceptacji. - 100write-spec
Zamienia pomysł na funkcję lub opis problemu w uporządkowaną specyfikację albo PRD z celami, wyłączeniami, metrykami sukcesu i testowalnymi kryteriami akceptacji. - 100prd-writer
Pisze albo ocenia PRD lub FRD: historyjki z kryteriami akceptacji, specyfikacje i wymagania przed przekazaniem do programistów. - 100workflow-prd-to-plan
Zamienia PRD w szczegółowy plan wdrożenia z historyjkami użytkownika, zadaniami dla każdej warstwy i kryteriami akceptacji. - 100create-prd
Tworzy dokument wymagań produktowych (PRD) dla nowej funkcji, gdy trzeba ją zaplanować.