feat: add Fagan Inspection semantic anchor (#issue)

Co-authored-by: rdmueller <1856308+rdmueller@users.noreply.github.com>

Author: Copilot

docs/anchors/fagan-inspection.adoc

@@ -0,0 +1,43 @@
+= Fagan Inspection
+:categories: testing-quality
+:roles: software-developer, qa-engineer, software-architect, team-lead
+:related: mutation-testing, testing-pyramid
+:proponents: Michael Fagan
+:tags: code-review, inspection, defect-detection, formal-review, static-analysis
+
+[%collapsible]
+====
+Also known as:: Formal Code Inspection, Software Inspection, Fagan's Inspection Method
+
+[discrete]
+== Core Concepts:
+
+Formal inspection process:: A structured, multi-phase review process for software artifacts (requirements, design, code) with defined roles and entry/exit criteria
+
+Roles:: Moderator (facilitates and logs), Author (created the artifact), Inspectors (reviewers), Recorder (documents defects)
+
+Six phases:: Planning → Overview → Preparation → Inspection Meeting → Rework → Follow-up
+
+Entry and exit criteria:: Explicit conditions that must be met before entering and leaving each phase, preventing premature progression
+
+Defect classification:: Defects are categorized by type (missing, wrong, extra) and severity, enabling process improvement through causal analysis
+
+Metrics-driven:: Inspection data (defect rate, inspection rate) are collected and used to improve both the product and the inspection process itself
+
+Key Proponents:: Michael Fagan ("Design and Code Inspections to Reduce Errors in Program Development", IBM Systems Journal, 1976)
+
+[discrete]
+== When to Use:
+
+* Safety-critical or high-assurance software where defect escape is costly
+* Reviewing requirements, architecture, design, or code artifacts early in development
+* Establishing a culture of quality and shared code ownership in teams
+* When you want measurable, process-level quality improvement over time
+* Regulated environments (medical devices, avionics, finance) requiring documented review evidence
+
+[discrete]
+== Related Anchors:
+
+* <<mutation-testing,Mutation Testing>>
+* <<testing-pyramid,Testing Pyramid>>
+====

docs/anchors/fagan-inspection.de.adoc

@@ -0,0 +1,43 @@
+= Fagan-Inspektion
+:categories: testing-quality
+:roles: software-developer, qa-engineer, software-architect, team-lead
+:related: mutation-testing, testing-pyramid
+:proponents: Michael Fagan
+:tags: code-review, inspection, defect-detection, formal-review, static-analysis
+
+[%collapsible]
+====
+Auch bekannt als:: Formale Code-Inspektion, Software-Inspektion, Fagan's Inspektionsmethode
+
+[discrete]
+== Kernkonzepte:
+
+Formaler Inspektionsprozess:: Ein strukturierter, mehrphasiger Prüfprozess für Software-Artefakte (Anforderungen, Design, Code) mit definierten Rollen und Ein-/Ausstiegskriterien
+
+Rollen:: Moderator (leitet und protokolliert), Autor (hat das Artefakt erstellt), Inspektoren (Prüfer), Protokollant (dokumentiert Defekte)
+
+Sechs Phasen:: Planung → Übersicht → Vorbereitung → Inspektionssitzung → Nachbearbeitung → Nachverfolgung
+
+Ein- und Ausstiegskriterien:: Explizite Bedingungen, die vor dem Eintritt in und Austritt aus jeder Phase erfüllt sein müssen, um vorzeitiges Voranschreiten zu verhindern
+
+Fehlerklassifikation:: Fehler werden nach Typ (fehlend, falsch, überflüssig) und Schweregrad kategorisiert, um Prozessverbesserungen durch Ursachenanalyse zu ermöglichen
+
+Kennzahlengetrieben:: Inspektionsdaten (Fehlerrate, Inspektionsrate) werden gesammelt und zur Verbesserung sowohl des Produkts als auch des Inspektionsprozesses genutzt
+
+Schlüsselvertreter:: Michael Fagan ("Design and Code Inspections to Reduce Errors in Program Development", IBM Systems Journal, 1976)
+
+[discrete]
+== Wann zu verwenden:
+
+* Sicherheitskritische oder qualitätsintensive Software, bei der das Entweichen von Fehlern kostspielig ist
+* Frühe Überprüfung von Anforderungen, Architektur, Design oder Code-Artefakten
+* Aufbau einer Qualitätskultur und gemeinsamen Code-Verantwortung im Team
+* Wenn messbare, prozessbasierte Qualitätsverbesserung über die Zeit angestrebt wird
+* Regulierte Umgebungen (Medizinprodukte, Luftfahrt, Finanzen), die dokumentierte Prüfnachweise erfordern
+
+[discrete]
+== Verwandte Anker:
+
+* <<mutation-testing,Mutation Testing>>
+* <<testing-pyramid,Testing Pyramid>>
+====

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

@@ -38,6 +38,11 @@ Source: https://github.com/LLM-Coding/Semantic-Anchors
 ### Property-Based Testing
 - **Core:** Test properties/invariants with generated inputs (QuickCheck, Hypothesis)
 
+### Fagan Inspection
+- **Also known as:** Formal Code Inspection, Software Inspection
+- **Proponents:** Michael Fagan
+- **Core:** Structured six-phase review process (Planning, Overview, Preparation, Inspection Meeting, Rework, Follow-up) with defined roles (Moderator, Author, Inspectors, Recorder), entry/exit criteria, and metrics-driven defect classification
+
 ### IEC 61508 SIL Levels
 - **Proponents:** International Electrotechnical Commission
 - **Core:** Safety integrity levels for safety-critical systems

website/public/data/anchors.json

@@ -303,7 +303,7 @@
   },
   {
     "id": "devils-advocate",
-    "title": "Devil’s Advocate",
+    "title": "Devil\u2019s Advocate",
     "categories": [
       "problem-solving"
     ],
@@ -320,7 +320,7 @@
   },
   {
     "id": "diataxis-framework",
-    "title": "Diátaxis Framework",
+    "title": "Di\u00e1taxis Framework",
     "categories": [
       "documentation"
     ],
@@ -335,7 +335,7 @@
   },
   {
     "id": "docs-as-code",
-    "title": "Docs-as-Code according to Ralf D. Müller",
+    "title": "Docs-as-Code according to Ralf D. M\u00fcller",
     "categories": [
       "documentation"
     ],
@@ -368,7 +368,7 @@
   },
   {
     "id": "dry-principle",
-    "title": "DRY (Don’t Repeat Yourself)",
+    "title": "DRY (Don\u2019t Repeat Yourself)",
     "categories": [
       "design-principles"
     ],
@@ -446,6 +446,34 @@
     "tags": [],
     "filePath": "docs/anchors/feynman-technique.adoc"
   },
+  {
+    "id": "fagan-inspection",
+    "title": "Fagan Inspection",
+    "categories": [
+      "testing-quality"
+    ],
+    "roles": [
+      "software-developer",
+      "qa-engineer",
+      "software-architect",
+      "team-lead"
+    ],
+    "related": [
+      "mutation-testing",
+      "testing-pyramid"
+    ],
+    "proponents": [
+      "Michael Fagan"
+    ],
+    "tags": [
+      "code-review",
+      "inspection",
+      "defect-detection",
+      "formal-review",
+      "static-analysis"
+    ],
+    "filePath": "docs/anchors/fagan-inspection.adoc"
+  },
   {
     "id": "five-whys",
     "title": "Five Whys (Ohno)",
@@ -509,7 +537,7 @@
       "tdd-london-school"
     ],
     "proponents": [
-      "Aslak Hellesøy"
+      "Aslak Helles\u00f8y"
     ],
     "tags": [
       "gherkin",
@@ -1284,9 +1312,9 @@
       "morphological-box"
     ],
     "proponents": [
-      "Jörg Becker",
+      "J\u00f6rg Becker",
       "Michael Rosemann",
-      "Rolf Schütte"
+      "Rolf Sch\u00fctte"
     ],
     "tags": [
       "modeling",
@@ -1411,7 +1439,7 @@
   },
   {
     "id": "lasr",
-    "title": "LASR according to Toth/Zörner",
+    "title": "LASR according to Toth/Z\u00f6rner",
     "categories": [
       "software-architecture"
     ],
@@ -1429,7 +1457,7 @@
     ],
     "proponents": [
       "Stefan Toth",
-      "Stefan Zörner"
+      "Stefan Z\u00f6rner"
     ],
     "tags": [
       "architecture-documentation",
@@ -2262,7 +2290,7 @@
   },
   {
     "id": "yagni",
-    "title": "YAGNI (You Aren’t Gonna Need It)",
+    "title": "YAGNI (You Aren\u2019t Gonna Need It)",
     "categories": [
       "design-principles"
     ],
@@ -2289,4 +2317,4 @@
     ],
     "filePath": "docs/anchors/yagni.adoc"
   }
-]
+]