Skip to content

Commit a9d8346

Browse files
rdmuellerrdmueller
authored
Merge pull request #188 from LLM-Coding/copilot/add-prd-anchor-term
feat: Add PRD (Product Requirements Document) semantic anchor
2 parents 0072493 + b9aa50b commit a9d8346

6 files changed

Lines changed: 143 additions & 0 deletions

File tree

‎docs/anchors/prd.adoc‎

Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,51 @@
1+
= PRD
2+
:categories: requirements-engineering
3+
:roles: product-owner, business-analyst, software-developer, team-lead
4+
:related: moscow, user-story-mapping, impact-mapping, ears-requirements
5+
:proponents: Marty Cagan, Roman Pichler
6+
:tags: product, requirements, specification, planning, stakeholders
7+
8+
[%collapsible]
9+
====
10+
Full Name:: Product Requirements Document
11+
12+
Also known as:: Product Spec, Feature Spec, Requirements Specification
13+
14+
[discrete]
15+
== *Core Concepts*:
16+
17+
Problem statement:: Clear articulation of the problem to be solved and the target users
18+
19+
Goals and success metrics:: Measurable outcomes that define what "done" looks like (KPIs, OKRs)
20+
21+
User personas and use cases:: Who will use the product and what they are trying to accomplish
22+
23+
Functional requirements:: What the system must do — features, behaviors, and capabilities
24+
25+
Non-functional requirements:: Quality attributes — performance, security, scalability, accessibility
26+
27+
Scope and out-of-scope:: Explicit boundaries to prevent scope creep and align stakeholders
28+
29+
Constraints and assumptions:: Technical, business, regulatory, or timeline constraints
30+
31+
Open questions:: Unresolved decisions or dependencies that must be tracked
32+
33+
Key Proponents:: Marty Cagan ("Inspired"), Roman Pichler ("Strategize")
34+
35+
[discrete]
36+
== *When to Use*:
37+
38+
* Before starting design or development of a new product or major feature
39+
* When aligning cross-functional teams (engineering, design, marketing, legal)
40+
* To provide a shared reference for scope negotiations and tradeoff decisions
41+
* When stakeholder sign-off or compliance documentation is required
42+
* As a living document updated throughout the product discovery process
43+
44+
[discrete]
45+
== *Related Anchors*:
46+
47+
* <<moscow,MoSCoW>>
48+
* <<user-story-mapping,User Story Mapping>>
49+
* <<impact-mapping,Impact Mapping>>
50+
* <<ears-requirements,EARS-Requirements>>
51+
====

‎docs/anchors/prd.de.adoc‎

Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,51 @@
1+
= PRD
2+
:categories: requirements-engineering
3+
:roles: product-owner, business-analyst, software-developer, team-lead
4+
:related: moscow, user-story-mapping, impact-mapping, ears-requirements
5+
:proponents: Marty Cagan, Roman Pichler
6+
:tags: product, requirements, specification, planning, stakeholders
7+
8+
[%collapsible]
9+
====
10+
Vollständiger Name:: Product Requirements Document (Produktanforderungsdokument)
11+
12+
Auch bekannt als:: Product Spec, Feature Spec, Anforderungsspezifikation
13+
14+
[discrete]
15+
== *Kernkonzepte*:
16+
17+
Problembeschreibung:: Klare Formulierung des zu lösenden Problems und der Zielnutzer
18+
19+
Ziele und Erfolgskennzahlen:: Messbare Ergebnisse, die definieren, was „fertig" bedeutet (KPIs, OKRs)
20+
21+
Nutzerpersonas und Anwendungsfälle:: Wer das Produkt nutzt und was die Nutzer erreichen möchten
22+
23+
Funktionale Anforderungen:: Was das System tun muss — Features, Verhalten und Fähigkeiten
24+
25+
Nicht-funktionale Anforderungen:: Qualitätsattribute — Performance, Sicherheit, Skalierbarkeit, Barrierefreiheit
26+
27+
Scope und Out-of-Scope:: Explizite Grenzen zur Vermeidung von Scope Creep und zur Abstimmung mit Stakeholdern
28+
29+
Einschränkungen und Annahmen:: Technische, geschäftliche, regulatorische oder zeitliche Einschränkungen
30+
31+
Offene Fragen:: Ungelöste Entscheidungen oder Abhängigkeiten, die verfolgt werden müssen
32+
33+
Schlüsselvertreter:: Marty Cagan ("Inspired"), Roman Pichler ("Strategize")
34+
35+
[discrete]
36+
== *Wann zu verwenden*:
37+
38+
* Vor Beginn von Design oder Entwicklung eines neuen Produkts oder eines größeren Features
39+
* Zur Abstimmung funktionsübergreifender Teams (Engineering, Design, Marketing, Recht)
40+
* Als gemeinsame Referenz für Scope-Verhandlungen und Abwägungsentscheidungen
41+
* Wenn Stakeholder-Freigabe oder Compliance-Dokumentation erforderlich ist
42+
* Als lebendes Dokument, das während des Produktentdeckungsprozesses aktualisiert wird
43+
44+
[discrete]
45+
== *Verwandte Anker*:
46+
47+
* <<moscow,MoSCoW>>
48+
* <<user-story-mapping,User Story Mapping>>
49+
* <<impact-mapping,Impact Mapping>>
50+
* <<ears-requirements,EARS-Requirements>>
51+
====

‎skill/semantic-anchor-translator/references/catalog.md‎

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -202,6 +202,11 @@ Source: https://github.com/LLM-Coding/Semantic-Anchors
202202

203203
## Requirements Engineering
204204

205+
### PRD
206+
- **Also known as:** Product Requirements Document, Product Spec, Feature Spec
207+
- **Proponents:** Marty Cagan, Roman Pichler
208+
- **Core:** Problem statement, goals & success metrics, user personas, functional & non-functional requirements, scope boundaries, constraints, open questions
209+
205210
### MoSCoW
206211
- **Proponents:** Dai Clegg
207212
- **Core:** Must have, Should have, Could have, Won't have

‎website/public/data/anchors.json‎

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1804,6 +1804,37 @@
18041804
"filePath": "docs/anchors/plain-english-strunk-white.adoc",
18051805
"tier": 3
18061806
},
1807+
{
1808+
"id": "prd",
1809+
"title": "PRD",
1810+
"categories": [
1811+
"requirements-engineering"
1812+
],
1813+
"roles": [
1814+
"product-owner",
1815+
"business-analyst",
1816+
"software-developer",
1817+
"team-lead"
1818+
],
1819+
"related": [
1820+
"moscow",
1821+
"user-story-mapping",
1822+
"impact-mapping",
1823+
"ears-requirements"
1824+
],
1825+
"proponents": [
1826+
"Marty Cagan",
1827+
"Roman Pichler"
1828+
],
1829+
"tags": [
1830+
"product",
1831+
"requirements",
1832+
"specification",
1833+
"planning",
1834+
"stakeholders"
1835+
],
1836+
"filePath": "docs/anchors/prd.adoc"
1837+
},
18071838
{
18081839
"id": "problem-space-nvc",
18091840
"title": "Nonviolent Communication (Rosenberg)",

‎website/public/data/categories.json‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -105,6 +105,7 @@
105105
"anchors": [
106106
"ears-requirements",
107107
"moscow",
108+
"prd",
108109
"problem-space-nvc",
109110
"user-story-mapping"
110111
]

‎website/public/data/roles.json‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,7 @@
1717
"mece",
1818
"moscow",
1919
"plain-english-strunk-white",
20+
"prd",
2021
"problem-space-nvc",
2122
"pyramid-principle",
2223
"regulated-environment",
@@ -123,6 +124,7 @@
123124
"morphological-box",
124125
"moscow",
125126
"myers-briggs-type-indicator",
127+
"prd",
126128
"problem-space-nvc",
127129
"pugh-matrix",
128130
"semantic-versioning",
@@ -276,6 +278,7 @@
276278
"mutation-testing",
277279
"owasp-top-10",
278280
"plain-english-strunk-white",
281+
"prd",
279282
"property-based-testing",
280283
"regulated-environment",
281284
"semantic-versioning",
@@ -325,6 +328,7 @@
325328
"moscow",
326329
"myers-briggs-type-indicator",
327330
"owasp-top-10",
331+
"prd",
328332
"problem-space-nvc",
329333
"pugh-matrix",
330334
"pyramid-principle",

0 commit comments

Comments
 (0)