Merge pull request #186 from LLM-Coding/copilot/add-definition-of-done-anchor

feat: Add "Definition of Done" semantic anchor

Author: rdmueller

docs/anchors/definition-of-done.adoc

@@ -0,0 +1,46 @@
+= Definition of Done
+:categories: development-workflow
+:roles: software-developer, qa-engineer, product-owner, team-lead
+:related: bdd-given-when-then, user-story-mapping, moscow
+:proponents: Ken Schwaber, Jeff Sutherland
+:tags: dod, acceptance criteria, scrum, agile, quality gates, done, sprint, increment
+
+[%collapsible]
+====
+Also known as:: DoD, Done Criteria, Acceptance Criteria (team-level)
+
+[discrete]
+== *Core Concepts*:
+
+Shared agreement:: A formal, team-wide checklist of quality criteria that every increment must satisfy before it is declared "done"
+
+Increment quality gates:: Concrete, verifiable conditions — e.g., code reviewed, tests passing, documentation updated, no known defects
+
+Transparency:: Makes the meaning of "done" visible and unambiguous to all stakeholders, preventing hidden technical debt
+
+Sprint-level vs. product-level DoD:: Teams may maintain separate DoD lists for Sprint increments and for releasable product increments
+
+Continuous refinement:: The DoD evolves as the team matures; stricter gates are added over time
+
+Undone work:: Work that does not meet the DoD is not counted as complete; it returns to the Product Backlog
+
+Shared responsibility:: The entire Scrum team (Developers, Product Owner, Scrum Master) owns and respects the DoD
+
+
+Key Proponents:: Ken Schwaber & Jeff Sutherland ("The Scrum Guide", 2020); Mike Cohn ("Succeeding with Agile", 2009)
+
+[discrete]
+== *When to Use*:
+
+* Establishing a consistent quality standard across a Scrum or agile team
+* Onboarding new team members so they understand what "finished" means
+* Reducing rework and late-cycle defects by agreeing on criteria upfront
+* Aligning developers, QA, and product owners on release readiness
+
+[discrete]
+== *Related Anchors*:
+
+* <<bdd-given-when-then,BDD (Behavior-Driven Development)>> - Given-When-Then scenarios that operationalize acceptance criteria
+* <<user-story-mapping,User Story Mapping>> - Planning technique that identifies the scope Definition of Done must cover
+* <<moscow,MoSCoW>> - Prioritization method used to decide which DoD items are must-haves
+====

docs/anchors/definition-of-done.de.adoc

@@ -0,0 +1,46 @@
+= Definition of Done
+:categories: development-workflow
+:roles: software-developer, qa-engineer, product-owner, team-lead
+:related: bdd-given-when-then, user-story-mapping, moscow
+:proponents: Ken Schwaber, Jeff Sutherland
+:tags: dod, acceptance criteria, scrum, agile, quality gates, done, sprint, increment
+
+[%collapsible]
+====
+Auch bekannt als:: DoD, Done-Kriterien, Akzeptanzkriterien (Teamebene)
+
+[discrete]
+== *Kernkonzepte*:
+
+Gemeinsame Vereinbarung:: Eine formelle, teamweite Checkliste von Qualitätskriterien, die jedes Inkrement erfüllen muss, bevor es als „fertig" gilt
+
+Inkrementelle Qualitätsgates:: Konkrete, überprüfbare Bedingungen — z. B. Code reviewed, Tests bestanden, Dokumentation aktualisiert, keine bekannten Defekte
+
+Transparenz:: Macht die Bedeutung von „fertig" für alle Stakeholder sichtbar und eindeutig und verhindert versteckte technische Schulden
+
+Sprint-DoD vs. Produkt-DoD:: Teams können separate DoD-Listen für Sprint-Inkremente und für auslieferbare Produktinkremente pflegen
+
+Kontinuierliche Verfeinerung:: Die DoD entwickelt sich mit der Teamreife weiter; im Laufe der Zeit werden strengere Gates hinzugefügt
+
+Nicht erledigte Arbeit:: Arbeit, die die DoD nicht erfüllt, gilt nicht als abgeschlossen und kehrt in den Product Backlog zurück
+
+Gemeinsame Verantwortung:: Das gesamte Scrum-Team (Entwickler, Product Owner, Scrum Master) besitzt und respektiert die DoD
+
+
+Schlüsselvertreter:: Ken Schwaber & Jeff Sutherland ("The Scrum Guide", 2020); Mike Cohn ("Succeeding with Agile", 2009)
+
+[discrete]
+== *Wann zu verwenden*:
+
+* Einrichtung eines konsistenten Qualitätsstandards in einem Scrum- oder agilen Team
+* Onboarding neuer Teammitglieder, damit sie verstehen, was „fertig" bedeutet
+* Reduzierung von Nacharbeit und späten Defekten durch vorherige Einigung auf Kriterien
+* Abstimmung von Entwicklern, QA und Product Ownern auf die Release-Bereitschaft
+
+[discrete]
+== *Verwandte Anker*:
+
+* <<bdd-given-when-then,BDD (Behavior-Driven Development)>> - Given-When-Then-Szenarien, die Akzeptanzkriterien operationalisieren
+* <<user-story-mapping,User Story Mapping>> - Planungstechnik, die den Umfang identifiziert, den die DoD abdecken muss
+* <<moscow,MoSCoW>> - Priorisierungsmethode, um zu entscheiden, welche DoD-Punkte Must-haves sind
+====

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

@@ -275,6 +275,11 @@ Source: https://github.com/LLM-Coding/Semantic-Anchors
 
 ## Development Workflow
 
+### Definition of Done
+- **Also known as:** DoD, Done Criteria
+- **Proponents:** Ken Schwaber, Jeff Sutherland
+- **Core:** Team-wide checklist of quality criteria every increment must satisfy; transparency on what "done" means; sprint-level vs. product-level DoD; prevents hidden technical debt
+
 ### GitHub Flow
 - **Proponents:** Scott Chacon
 - **Core:** Branch-based workflow — short-lived feature branches, Pull Request reviews, `main` always deployable, merge triggers immediate deployment

website/public/data/anchors.json

@@ -289,6 +289,39 @@
     "filePath": "docs/anchors/cynefin-framework.adoc",
     "tier": 3
   },
+  {
+    "id": "definition-of-done",
+    "title": "Definition of Done",
+    "categories": [
+      "development-workflow"
+    ],
+    "roles": [
+      "software-developer",
+      "qa-engineer",
+      "product-owner",
+      "team-lead"
+    ],
+    "related": [
+      "bdd-given-when-then",
+      "user-story-mapping",
+      "moscow"
+    ],
+    "proponents": [
+      "Ken Schwaber",
+      "Jeff Sutherland"
+    ],
+    "tags": [
+      "dod",
+      "acceptance criteria",
+      "scrum",
+      "agile",
+      "quality gates",
+      "done",
+      "sprint",
+      "increment"
+    ],
+    "filePath": "docs/anchors/definition-of-done.adoc"
+  },
   {
     "id": "devils-advocate",
     "title": "Devil\u2019s Advocate",