[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-azure-sdaf-ha-diagnostics":3,"mdc--2xxs6q-key":35,"related-repo-azure-sdaf-ha-diagnostics":596,"related-org-azure-sdaf-ha-diagnostics":681},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":12,"stars":24,"repoUrl":25,"updatedAt":26,"license":27,"forks":28,"topics":29,"repo":30,"sourceUrl":33,"mdContent":34},"sdaf-ha-diagnostics","diagnose SDAF high-availability cluster failures","Diagnose a live or recently failed SDAF high-availability cluster without changing cluster state. Start read-first: capture `crm status full` or `pcs status --full`, inspect SBD or fencing evidence, confirm current resource placement, and reuse existing quality-assurance or HCMT artifacts. Grounded in `docs\u002Flocal\u002F07-10-quality-assurance.md`, the shipped Pacemaker role vars\u002Ftasks, and the SAP Automation QA setup role. Use when a user says \"diagnose my HANA failover\", \"crm status\", \"pcs status\", \"check fencing\", \"why is the SCS\u002FERS cluster unhealthy\", \"offline_validation\u002Fcib\", or \"review an HCMT result zip\". Do NOT use for pre-deploy topology or design choices (see `sdaf-ha-topology`), fresh installation\u002Fdeploy, or disruptive failover\u002Ffencing exercises (see `sdaf-quality-assurance`).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},"azure","Azure (Microsoft)","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fazure.png","Azure",[13,17,18,21],{"name":14,"slug":15,"type":16},"Operations","operations","tag",{"name":11,"slug":8,"type":16},{"name":19,"slug":20,"type":16},"Diagnostics","diagnostics",{"name":22,"slug":23,"type":16},"SAP","sap",143,"https:\u002F\u002Fgithub.com\u002FAzure\u002Fsap-automation","2026-09-02T07:48:04.154501","MIT",173,[],{"repoUrl":25,"stars":24,"forks":28,"topics":31,"description":32},[],"This is the repository supporting the SAP deployment automation framework on Azure","https:\u002F\u002Fgithub.com\u002FAzure\u002Fsap-automation\u002Ftree\u002FHEAD\u002Fskills\u002Fsdaf-ha-diagnostics","---\nname: sdaf-ha-diagnostics\ndescription: >\n  Diagnose a live or recently failed SDAF high-availability cluster without\n  changing cluster state. Start read-first: capture `crm status full` or\n  `pcs status --full`, inspect SBD or fencing evidence, confirm current\n  resource placement, and reuse existing quality-assurance or HCMT artifacts.\n  Grounded in `docs\u002Flocal\u002F07-10-quality-assurance.md`, the shipped Pacemaker\n  role vars\u002Ftasks, and the SAP Automation QA setup role. Use when a user says\n  \"diagnose my HANA failover\", \"crm status\", \"pcs status\", \"check fencing\",\n  \"why is the SCS\u002FERS cluster unhealthy\", \"offline_validation\u002Fcib\", or\n  \"review an HCMT result zip\". Do NOT use for pre-deploy topology or design\n  choices (see `sdaf-ha-topology`), fresh installation\u002Fdeploy, or disruptive\n  failover\u002Ffencing exercises (see `sdaf-quality-assurance`).\nallowed-tools: shell\nlicense: MIT\n---\n\n# SDAF HA Diagnostics\n\nAction-loop skill. Owns **read-first, safe diagnostics** for a live or\nrecently failed SDAF HA cluster. It does not choose the topology, move\nresources, clean up stonith history, or invent a recovery procedure.\n\nFor the exact evidence ladder, current-code anchors, and stop-list, read\n[`references\u002Fcluster-evidence.md`](references\u002Fcluster-evidence.md).\n\n## When to invoke\n\nTrigger on: \"diagnose HA cluster\", \"HANA failover failed\", \"crm status\",\n\"pcs status\", \"check fencing\", \"resource placement\", \"cluster unhealthy\",\n\"offline_validation\u002Fcib\", \"HCMT result\", \"SCS\u002FERS failover\", or \"read the\ncurrent Pacemaker state\".\n\nDo NOT trigger on:\n\n- pre-deploy design questions such as SBD vs Azure fence agent, ANF vs AFS,\n  ANGI eligibility, distro choice, or scale-out design — route to\n  `sdaf-ha-topology`;\n- requests to run online failover, crash, fencing, or blocked-network tests —\n  route to `sdaf-quality-assurance`;\n- a broader SDAF run failure whose primary symptom is the stage execution\n  itself — route to `sdaf-failure-triage`.\n\n## Preconditions\n\nAsk for the layer under test (HANA DB HA or SCS\u002FERS HA), OS family, evidence\ntype (live cluster, captured bundle, or prior test run), and any existing\n`crm` \u002F `pcs` output, QA reports, execution logs, or HCMT bundles. If cluster\nstate was already changed manually, preserve who changed what and when before\ndiagnosing anything else.\n\n## Recipe\n\n### Step 1 — classify the request before touching the cluster\n\nPick one lane:\n\n1. **Live read-only diagnosis** — explain current cluster state from status,\n   placement, and existing logs.\n2. **Captured artefact review** — read an existing `offline_validation` bundle,\n   QA report, or HCMT result without acting on the running cluster.\n3. **Framework-run or disruptive validation** — route to\n   `sdaf-quality-assurance`; the online functional tests stop resources, move\n   groups, fence nodes, and crash processes.\n4. **Topology\u002Fdesign** — route to `sdaf-ha-topology`.\n5. **Stage\u002Frun failure** — route to `sdaf-failure-triage`.\n\n### Step 2 — collect read-only evidence first\n\nUse the evidence ladder in\n[`references\u002Fcluster-evidence.md`](references\u002Fcluster-evidence.md). Minimum\nsafe evidence is:\n\n- OS-specific status: `crm status full` on SUSE or `pcs status --full` on\n  Red Hat;\n- current placement evidence such as `crm_resource --locate` for SCS\u002FERS;\n- existing fencing, SBD, or HANA hook-verification evidence;\n- existing QA, offline `cib`, and HCMT artefacts.\n\nPreserve raw output, host, and timestamp. Do not paraphrase away the cluster's\nown wording.\n\n### Step 3 — map the evidence to the right owner\n\n- **Stay in this skill** for read-only interpretation of current Pacemaker\n  state, placement, fencing\u002FSBD evidence, hook traces, or existing QA\u002FHCMT\n  artefacts.\n- **Route to `sdaf-quality-assurance`** to run configuration checks, offline HA\n  validation from captured `offline_validation\u002F\u003Chost>\u002Fcib` bundles, or\n  disruptive online HA exercises in an approved maintenance window.\n- **Route to `sdaf-failure-triage`** for failed SDAF runs or install-phase\n  assertions such as missing fencing SPN details, cluster password, or\n  required clustering scripts.\n- **Route to `sdaf-ha-topology`** when the question is what the cluster\n  *should* look like rather than what the current evidence says.\n\n### Step 4 — stop before state changes\n\nThe current codebase contains state-changing cluster actions in validation and\npost-provision tasks. This skill is **not** the place to run them.\n\nThe explicit stop-list lives in the reference. From this skill do **not**\nexecute `crm\u002Fpcs resource move`, `stonith_admin --cleanup`, role-defined\ncluster cleanup, `StartService`, `StartSystem ALL`, or online functional HA\ntests. If the user asks for recovery or failover action, stop at evidence\ncollection and routing; do not invent or approve a repair step.\n\n## Hard rules\n\n- Read-first only. Start with existing cluster status, logs, and artefacts.\n- Documented\u002Fcurrent-code only (D19). If the docs or shipped roles do not\n  describe a diagnostic path, say so and stop.\n- Do not invent recovery commands, failover steps, or cleanup procedures.\n- Keep topology and design separate; route those questions to\n  `sdaf-ha-topology`.\n- Treat disruptive validation as a separate workflow owned by\n  `sdaf-quality-assurance`.\n\n## What this skill does NOT do\n\n- Does not choose SBD vs Azure fence agent, storage, distro, ANGI, or\n  scale-out design.\n- Does not build, rebuild, reinstall, or actively fail over the cluster.\n- Does not treat HCMT as the first diagnostic step; it only reuses existing\n  HCMT artefacts if they are already present.\n\n## See also\n\n- `sdaf-ha-topology`\n- `sdaf-quality-assurance`\n- `sdaf-failure-triage`\n- `docs\u002Flocal\u002F07-10-quality-assurance.md`\n",{"data":36,"body":38},{"name":4,"description":6,"allowed-tools":37,"license":27},"shell",{"type":39,"children":40},"root",[41,49,63,81,88,93,98,140,146,167,173,180,185,265,271,286,341,346,352,424,430,442,484,490,530,536,554,560],{"type":42,"tag":43,"props":44,"children":45},"element","h1",{"id":4},[46],{"type":47,"value":48},"text","SDAF HA Diagnostics",{"type":42,"tag":50,"props":51,"children":52},"p",{},[53,55,61],{"type":47,"value":54},"Action-loop skill. Owns ",{"type":42,"tag":56,"props":57,"children":58},"strong",{},[59],{"type":47,"value":60},"read-first, safe diagnostics",{"type":47,"value":62}," for a live or\nrecently failed SDAF HA cluster. It does not choose the topology, move\nresources, clean up stonith history, or invent a recovery procedure.",{"type":42,"tag":50,"props":64,"children":65},{},[66,68,79],{"type":47,"value":67},"For the exact evidence ladder, current-code anchors, and stop-list, read\n",{"type":42,"tag":69,"props":70,"children":72},"a",{"href":71},"references\u002Fcluster-evidence.md",[73],{"type":42,"tag":74,"props":75,"children":77},"code",{"className":76},[],[78],{"type":47,"value":71},{"type":47,"value":80},".",{"type":42,"tag":82,"props":83,"children":85},"h2",{"id":84},"when-to-invoke",[86],{"type":47,"value":87},"When to invoke",{"type":42,"tag":50,"props":89,"children":90},{},[91],{"type":47,"value":92},"Trigger on: \"diagnose HA cluster\", \"HANA failover failed\", \"crm status\",\n\"pcs status\", \"check fencing\", \"resource placement\", \"cluster unhealthy\",\n\"offline_validation\u002Fcib\", \"HCMT result\", \"SCS\u002FERS failover\", or \"read the\ncurrent Pacemaker state\".",{"type":42,"tag":50,"props":94,"children":95},{},[96],{"type":47,"value":97},"Do NOT trigger on:",{"type":42,"tag":99,"props":100,"children":101},"ul",{},[102,116,128],{"type":42,"tag":103,"props":104,"children":105},"li",{},[106,108,114],{"type":47,"value":107},"pre-deploy design questions such as SBD vs Azure fence agent, ANF vs AFS,\nANGI eligibility, distro choice, or scale-out design — route to\n",{"type":42,"tag":74,"props":109,"children":111},{"className":110},[],[112],{"type":47,"value":113},"sdaf-ha-topology",{"type":47,"value":115},";",{"type":42,"tag":103,"props":117,"children":118},{},[119,121,127],{"type":47,"value":120},"requests to run online failover, crash, fencing, or blocked-network tests —\nroute to ",{"type":42,"tag":74,"props":122,"children":124},{"className":123},[],[125],{"type":47,"value":126},"sdaf-quality-assurance",{"type":47,"value":115},{"type":42,"tag":103,"props":129,"children":130},{},[131,133,139],{"type":47,"value":132},"a broader SDAF run failure whose primary symptom is the stage execution\nitself — route to ",{"type":42,"tag":74,"props":134,"children":136},{"className":135},[],[137],{"type":47,"value":138},"sdaf-failure-triage",{"type":47,"value":80},{"type":42,"tag":82,"props":141,"children":143},{"id":142},"preconditions",[144],{"type":47,"value":145},"Preconditions",{"type":42,"tag":50,"props":147,"children":148},{},[149,151,157,159,165],{"type":47,"value":150},"Ask for the layer under test (HANA DB HA or SCS\u002FERS HA), OS family, evidence\ntype (live cluster, captured bundle, or prior test run), and any existing\n",{"type":42,"tag":74,"props":152,"children":154},{"className":153},[],[155],{"type":47,"value":156},"crm",{"type":47,"value":158}," \u002F ",{"type":42,"tag":74,"props":160,"children":162},{"className":161},[],[163],{"type":47,"value":164},"pcs",{"type":47,"value":166}," output, QA reports, execution logs, or HCMT bundles. If cluster\nstate was already changed manually, preserve who changed what and when before\ndiagnosing anything else.",{"type":42,"tag":82,"props":168,"children":170},{"id":169},"recipe",[171],{"type":47,"value":172},"Recipe",{"type":42,"tag":174,"props":175,"children":177},"h3",{"id":176},"step-1-classify-the-request-before-touching-the-cluster",[178],{"type":47,"value":179},"Step 1 — classify the request before touching the cluster",{"type":42,"tag":50,"props":181,"children":182},{},[183],{"type":47,"value":184},"Pick one lane:",{"type":42,"tag":186,"props":187,"children":188},"ol",{},[189,199,217,234,250],{"type":42,"tag":103,"props":190,"children":191},{},[192,197],{"type":42,"tag":56,"props":193,"children":194},{},[195],{"type":47,"value":196},"Live read-only diagnosis",{"type":47,"value":198}," — explain current cluster state from status,\nplacement, and existing logs.",{"type":42,"tag":103,"props":200,"children":201},{},[202,207,209,215],{"type":42,"tag":56,"props":203,"children":204},{},[205],{"type":47,"value":206},"Captured artefact review",{"type":47,"value":208}," — read an existing ",{"type":42,"tag":74,"props":210,"children":212},{"className":211},[],[213],{"type":47,"value":214},"offline_validation",{"type":47,"value":216}," bundle,\nQA report, or HCMT result without acting on the running cluster.",{"type":42,"tag":103,"props":218,"children":219},{},[220,225,227,232],{"type":42,"tag":56,"props":221,"children":222},{},[223],{"type":47,"value":224},"Framework-run or disruptive validation",{"type":47,"value":226}," — route to\n",{"type":42,"tag":74,"props":228,"children":230},{"className":229},[],[231],{"type":47,"value":126},{"type":47,"value":233},"; the online functional tests stop resources, move\ngroups, fence nodes, and crash processes.",{"type":42,"tag":103,"props":235,"children":236},{},[237,242,244,249],{"type":42,"tag":56,"props":238,"children":239},{},[240],{"type":47,"value":241},"Topology\u002Fdesign",{"type":47,"value":243}," — route to ",{"type":42,"tag":74,"props":245,"children":247},{"className":246},[],[248],{"type":47,"value":113},{"type":47,"value":80},{"type":42,"tag":103,"props":251,"children":252},{},[253,258,259,264],{"type":42,"tag":56,"props":254,"children":255},{},[256],{"type":47,"value":257},"Stage\u002Frun failure",{"type":47,"value":243},{"type":42,"tag":74,"props":260,"children":262},{"className":261},[],[263],{"type":47,"value":138},{"type":47,"value":80},{"type":42,"tag":174,"props":266,"children":268},{"id":267},"step-2-collect-read-only-evidence-first",[269],{"type":47,"value":270},"Step 2 — collect read-only evidence first",{"type":42,"tag":50,"props":272,"children":273},{},[274,276,284],{"type":47,"value":275},"Use the evidence ladder in\n",{"type":42,"tag":69,"props":277,"children":278},{"href":71},[279],{"type":42,"tag":74,"props":280,"children":282},{"className":281},[],[283],{"type":47,"value":71},{"type":47,"value":285},". Minimum\nsafe evidence is:",{"type":42,"tag":99,"props":287,"children":288},{},[289,310,323,328],{"type":42,"tag":103,"props":290,"children":291},{},[292,294,300,302,308],{"type":47,"value":293},"OS-specific status: ",{"type":42,"tag":74,"props":295,"children":297},{"className":296},[],[298],{"type":47,"value":299},"crm status full",{"type":47,"value":301}," on SUSE or ",{"type":42,"tag":74,"props":303,"children":305},{"className":304},[],[306],{"type":47,"value":307},"pcs status --full",{"type":47,"value":309}," on\nRed Hat;",{"type":42,"tag":103,"props":311,"children":312},{},[313,315,321],{"type":47,"value":314},"current placement evidence such as ",{"type":42,"tag":74,"props":316,"children":318},{"className":317},[],[319],{"type":47,"value":320},"crm_resource --locate",{"type":47,"value":322}," for SCS\u002FERS;",{"type":42,"tag":103,"props":324,"children":325},{},[326],{"type":47,"value":327},"existing fencing, SBD, or HANA hook-verification evidence;",{"type":42,"tag":103,"props":329,"children":330},{},[331,333,339],{"type":47,"value":332},"existing QA, offline ",{"type":42,"tag":74,"props":334,"children":336},{"className":335},[],[337],{"type":47,"value":338},"cib",{"type":47,"value":340},", and HCMT artefacts.",{"type":42,"tag":50,"props":342,"children":343},{},[344],{"type":47,"value":345},"Preserve raw output, host, and timestamp. Do not paraphrase away the cluster's\nown wording.",{"type":42,"tag":174,"props":347,"children":349},{"id":348},"step-3-map-the-evidence-to-the-right-owner",[350],{"type":47,"value":351},"Step 3 — map the evidence to the right owner",{"type":42,"tag":99,"props":353,"children":354},{},[355,365,388,402],{"type":42,"tag":103,"props":356,"children":357},{},[358,363],{"type":42,"tag":56,"props":359,"children":360},{},[361],{"type":47,"value":362},"Stay in this skill",{"type":47,"value":364}," for read-only interpretation of current Pacemaker\nstate, placement, fencing\u002FSBD evidence, hook traces, or existing QA\u002FHCMT\nartefacts.",{"type":42,"tag":103,"props":366,"children":367},{},[368,378,380,386],{"type":42,"tag":56,"props":369,"children":370},{},[371,373],{"type":47,"value":372},"Route to ",{"type":42,"tag":74,"props":374,"children":376},{"className":375},[],[377],{"type":47,"value":126},{"type":47,"value":379}," to run configuration checks, offline HA\nvalidation from captured ",{"type":42,"tag":74,"props":381,"children":383},{"className":382},[],[384],{"type":47,"value":385},"offline_validation\u002F\u003Chost>\u002Fcib",{"type":47,"value":387}," bundles, or\ndisruptive online HA exercises in an approved maintenance window.",{"type":42,"tag":103,"props":389,"children":390},{},[391,400],{"type":42,"tag":56,"props":392,"children":393},{},[394,395],{"type":47,"value":372},{"type":42,"tag":74,"props":396,"children":398},{"className":397},[],[399],{"type":47,"value":138},{"type":47,"value":401}," for failed SDAF runs or install-phase\nassertions such as missing fencing SPN details, cluster password, or\nrequired clustering scripts.",{"type":42,"tag":103,"props":403,"children":404},{},[405,414,416,422],{"type":42,"tag":56,"props":406,"children":407},{},[408,409],{"type":47,"value":372},{"type":42,"tag":74,"props":410,"children":412},{"className":411},[],[413],{"type":47,"value":113},{"type":47,"value":415}," when the question is what the cluster\n",{"type":42,"tag":417,"props":418,"children":419},"em",{},[420],{"type":47,"value":421},"should",{"type":47,"value":423}," look like rather than what the current evidence says.",{"type":42,"tag":174,"props":425,"children":427},{"id":426},"step-4-stop-before-state-changes",[428],{"type":47,"value":429},"Step 4 — stop before state changes",{"type":42,"tag":50,"props":431,"children":432},{},[433,435,440],{"type":47,"value":434},"The current codebase contains state-changing cluster actions in validation and\npost-provision tasks. This skill is ",{"type":42,"tag":56,"props":436,"children":437},{},[438],{"type":47,"value":439},"not",{"type":47,"value":441}," the place to run them.",{"type":42,"tag":50,"props":443,"children":444},{},[445,447,451,453,459,461,467,469,475,476,482],{"type":47,"value":446},"The explicit stop-list lives in the reference. From this skill do ",{"type":42,"tag":56,"props":448,"children":449},{},[450],{"type":47,"value":439},{"type":47,"value":452},"\nexecute ",{"type":42,"tag":74,"props":454,"children":456},{"className":455},[],[457],{"type":47,"value":458},"crm\u002Fpcs resource move",{"type":47,"value":460},", ",{"type":42,"tag":74,"props":462,"children":464},{"className":463},[],[465],{"type":47,"value":466},"stonith_admin --cleanup",{"type":47,"value":468},", role-defined\ncluster cleanup, ",{"type":42,"tag":74,"props":470,"children":472},{"className":471},[],[473],{"type":47,"value":474},"StartService",{"type":47,"value":460},{"type":42,"tag":74,"props":477,"children":479},{"className":478},[],[480],{"type":47,"value":481},"StartSystem ALL",{"type":47,"value":483},", or online functional HA\ntests. If the user asks for recovery or failover action, stop at evidence\ncollection and routing; do not invent or approve a repair step.",{"type":42,"tag":82,"props":485,"children":487},{"id":486},"hard-rules",[488],{"type":47,"value":489},"Hard rules",{"type":42,"tag":99,"props":491,"children":492},{},[493,498,503,508,519],{"type":42,"tag":103,"props":494,"children":495},{},[496],{"type":47,"value":497},"Read-first only. Start with existing cluster status, logs, and artefacts.",{"type":42,"tag":103,"props":499,"children":500},{},[501],{"type":47,"value":502},"Documented\u002Fcurrent-code only (D19). If the docs or shipped roles do not\ndescribe a diagnostic path, say so and stop.",{"type":42,"tag":103,"props":504,"children":505},{},[506],{"type":47,"value":507},"Do not invent recovery commands, failover steps, or cleanup procedures.",{"type":42,"tag":103,"props":509,"children":510},{},[511,513,518],{"type":47,"value":512},"Keep topology and design separate; route those questions to\n",{"type":42,"tag":74,"props":514,"children":516},{"className":515},[],[517],{"type":47,"value":113},{"type":47,"value":80},{"type":42,"tag":103,"props":520,"children":521},{},[522,524,529],{"type":47,"value":523},"Treat disruptive validation as a separate workflow owned by\n",{"type":42,"tag":74,"props":525,"children":527},{"className":526},[],[528],{"type":47,"value":126},{"type":47,"value":80},{"type":42,"tag":82,"props":531,"children":533},{"id":532},"what-this-skill-does-not-do",[534],{"type":47,"value":535},"What this skill does NOT do",{"type":42,"tag":99,"props":537,"children":538},{},[539,544,549],{"type":42,"tag":103,"props":540,"children":541},{},[542],{"type":47,"value":543},"Does not choose SBD vs Azure fence agent, storage, distro, ANGI, or\nscale-out design.",{"type":42,"tag":103,"props":545,"children":546},{},[547],{"type":47,"value":548},"Does not build, rebuild, reinstall, or actively fail over the cluster.",{"type":42,"tag":103,"props":550,"children":551},{},[552],{"type":47,"value":553},"Does not treat HCMT as the first diagnostic step; it only reuses existing\nHCMT artefacts if they are already present.",{"type":42,"tag":82,"props":555,"children":557},{"id":556},"see-also",[558],{"type":47,"value":559},"See also",{"type":42,"tag":99,"props":561,"children":562},{},[563,571,579,587],{"type":42,"tag":103,"props":564,"children":565},{},[566],{"type":42,"tag":74,"props":567,"children":569},{"className":568},[],[570],{"type":47,"value":113},{"type":42,"tag":103,"props":572,"children":573},{},[574],{"type":42,"tag":74,"props":575,"children":577},{"className":576},[],[578],{"type":47,"value":126},{"type":42,"tag":103,"props":580,"children":581},{},[582],{"type":42,"tag":74,"props":583,"children":585},{"className":584},[],[586],{"type":47,"value":138},{"type":42,"tag":103,"props":588,"children":589},{},[590],{"type":42,"tag":74,"props":591,"children":593},{"className":592},[],[594],{"type":47,"value":595},"docs\u002Flocal\u002F07-10-quality-assurance.md",{"items":597,"total":680},[598,610,625,638,645,657,667],{"slug":599,"name":599,"fn":600,"description":601,"org":602,"tags":603,"stars":24,"repoUrl":25,"updatedAt":609},"sdaf-bom-selection","select SAP Bill of Materials","Pick the right SDAF BOM for a target SAP product \u002F release \u002F DB platform \u002F version \u002F kernel \u002F topology. Explains where BOMs live in the samples repo (`SAP\u002F` for whole products, `BOM\u002F` for components), decodes the `ms`, `v####`, and `latest` suffix conventions, points at the compatibility guardrails (`supportedPlatforms`, `supportedDBVersions`, `supportedKernels`), and reminds the operator that the download flow needs four explicit BOM keys in `sap-parameters.yaml`. Use when a user says \"which BOM do I use\", \"product BOM vs component BOM\", \"SAP samples BOM catalog\", \"BOM_CATALOG\", \"S4\u002F2023 BOM\", \"HANA BOM\", or \"how do I pick a BOM for HANA\u002FOracle\u002FDB2\u002FASE\". Do NOT use to author a new BOM, to acquire media (`sdaf-media-acquisition`), or to troubleshoot a checksum \u002F 404 (`sdaf-media-diagnostics`).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[604,605,608],{"name":11,"slug":8,"type":16},{"name":606,"slug":607,"type":16},"Configuration","configuration",{"name":22,"slug":23,"type":16},"2026-09-02T07:47:45.597063",{"slug":611,"name":611,"fn":612,"description":613,"org":614,"tags":615,"stars":24,"repoUrl":25,"updatedAt":624},"sdaf-control-plane-bootstrap","deploy SDAF control plane infrastructure","Deploy the SDAF control plane locally: prepare DEPLOYER and LIBRARY tfvars, review the plan, run `deploy_controlplane.sh` per `docs\u002Flocal\u002F03-00-control-plane.md § Run`, and validate the deployer + library + state hand-off. Grounded in `docs\u002Flocal\u002F03-00-control-plane.md`. Use when a user says \"deploy the SDAF control plane\", \"run deploy_controlplane.sh\", \"bootstrap SDAF from an empty subscription\", \"install the deployer\" or \"create the SAP library\". Do NOT use for workload zone (see sdaf-workload-zone), SAP system (see sdaf-sap-system), removal (`sdaf-safe-removal`), or Azure Government \u002F sovereign-cloud deltas (`sdaf-sovereign-cloud`).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[616,617,620,623],{"name":11,"slug":8,"type":16},{"name":618,"slug":619,"type":16},"Deployment","deployment",{"name":621,"slug":622,"type":16},"Infrastructure","infrastructure",{"name":22,"slug":23,"type":16},"2026-09-02T07:46:51.573641",{"slug":138,"name":138,"fn":626,"description":627,"org":628,"tags":629,"stars":24,"repoUrl":25,"updatedAt":637},"triage failed SAP automation runs","Triage a failed or suspicious SDAF run: distinguish a real failure from a green no-op or a clean plan reported as failure, map the observed symptom to a documented cause in `docs\u002Flocal\u002Ftroubleshooting.md`, and hand off to the stage-owning skill for retry. Use when a user says \"SDAF run failed\", \"my deploy exited non-zero\", \"the plan was clean but exit 1\", \"the run said success but nothing was deployed\", \"state lock error\", \"unexpected replacement\", \"control plane stopped partway\", \"generated hosts.yaml missing\", \"workload-zone private endpoint failure\", \"workload-zone subnet policy failure\", or \"SDAF exit 2\". Do NOT use to actually deploy or to redesign the workspace layout.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[630,631,632,633,634],{"name":11,"slug":8,"type":16},{"name":19,"slug":20,"type":16},{"name":14,"slug":15,"type":16},{"name":22,"slug":23,"type":16},{"name":635,"slug":636,"type":16},"Triage","triage","2026-09-02T07:47:40.607437",{"slug":4,"name":4,"fn":5,"description":6,"org":639,"tags":640,"stars":24,"repoUrl":25,"updatedAt":26},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[641,642,643,644],{"name":11,"slug":8,"type":16},{"name":19,"slug":20,"type":16},{"name":14,"slug":15,"type":16},{"name":22,"slug":23,"type":16},{"slug":113,"name":113,"fn":646,"description":647,"org":648,"tags":649,"stars":24,"repoUrl":25,"updatedAt":656},"design high-availability SAP topologies","Choose the documented SDAF high-availability design before SAP-system deployment. Use when a user asks which HA topology to deploy, whether to use AFA or SBD, AFS or ANF, HANA scale-up or scale-out, whether ANGI is allowed, or which HA inputs must be set before deployment. Ground answers in the current support matrix, Ansible roles, sample tfvars, and validation logic. Do NOT use for live cluster diagnosis (sdaf-ha-diagnostics) or for running the installers (sdaf-sap-installation).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[650,653,654,655],{"name":651,"slug":652,"type":16},"Architecture","architecture",{"name":11,"slug":8,"type":16},{"name":621,"slug":622,"type":16},{"name":22,"slug":23,"type":16},"2026-09-02T07:47:43.405138",{"slug":658,"name":658,"fn":659,"description":660,"org":661,"tags":662,"stars":24,"repoUrl":25,"updatedAt":666},"sdaf-media-acquisition","acquire SAP installation media","Acquire approved SAP media into the SDAF library after SAP-system infrastructure exists. Drives local `deploy\u002Fansible\u002Fdownload_menu.sh` per `docs\u002Flocal\u002F06-00-software-and-installation.md § Download software`, enforces the documented `BOM_CATALOG` root and the four required `sap-parameters.yaml` BOM keys (`application_bom_name`, `database_bom_name`, `sap_kernel_bom_name`, `save_bom_as`), and explains the documented download and validation flow. Use for \"download SAP media\", \"run download_menu.sh\", \"acquire software into the library\", \"BOM Downloader\", \"BOM_CATALOG\", or \"assemble application\u002Fdatabase\u002Fkernel BOMs for download\". Do NOT use to choose a BOM, troubleshoot a failed download, or run installation playbooks.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[663,664,665],{"name":11,"slug":8,"type":16},{"name":14,"slug":15,"type":16},{"name":22,"slug":23,"type":16},"2026-09-02T07:46:44.504107",{"slug":668,"name":668,"fn":669,"description":670,"org":671,"tags":672,"stars":24,"repoUrl":25,"updatedAt":679},"sdaf-media-diagnostics","diagnose SDAF media and BOM processing","Diagnose SDAF software-download and BOM-processing failures after a BOM is already selected. Covers the documented local media path, SAP download, storage-account upload\u002Fdownload, checksum validation, and `SAPCAR` \u002F `.EXE` extraction. Use when a user says \"download_menu failed\", \"BOM downloader 404\", \"missing archive\", \"checksum mismatch\", \"SAPCAR failed\", \"bom-processing-done missing\", or \"my SPS07 media run can't find a file\". Do NOT use to choose a BOM (see `sdaf-bom-selection`), to run a clean first-time media download with no failure, or to diagnose a later non-media install failure.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[673,674,675,676],{"name":11,"slug":8,"type":16},{"name":19,"slug":20,"type":16},{"name":22,"slug":23,"type":16},{"name":677,"slug":678,"type":16},"Storage","storage","2026-09-02T07:48:06.369058",18,{"items":682,"total":812},[683,702,719,725,732,740,747,754,760,767,780,800],{"slug":684,"name":684,"fn":685,"description":686,"org":687,"tags":688,"stars":699,"repoUrl":700,"updatedAt":701},"azure-arg-external-evaluation-policy-author","author and test Azure Resource Graph policies","Use when the user wants to author, design, or test an Azure Policy that queries Azure Resource Graph (ARG) at request-time — i.e. a policy whose deny\u002Faudit decision depends on data from elsewhere in the subscription (sibling\u002Fparent resource state, RG-wide invariants, multi-hop relationships, etc.). Formally called Azure Policy External Evaluation; sometimes referred to colloquially as \"Invoke\". Drives an iterative KQL co-design loop against the user's real subscription via `az graph query`, then emits a policy definition, assignment, `.http` test flow, and an `EXPLANATION.md` companion. Read-only; never provisions anything.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[689,690,693,696],{"name":11,"slug":8,"type":16},{"name":691,"slug":692,"type":16},"Compliance","compliance",{"name":694,"slug":695,"type":16},"Governance","governance",{"name":697,"slug":698,"type":16},"Policy","policy",1689,"https:\u002F\u002Fgithub.com\u002FAzure\u002Fazure-policy","2026-07-12T08:17:48.378432",{"slug":703,"name":703,"fn":704,"description":705,"org":706,"tags":707,"stars":716,"repoUrl":717,"updatedAt":718},"azure-blueprints-migration","migrate Azure Blueprints to Template Specs","Use when a user needs to migrate off Azure Blueprints (definitions and\u002For assignments) to Template Specs and Deployment Stacks before the January 31, 2027 retirement. Covers inventory, export, conversion to Bicep, policy decoupling, Template Spec publishing, Deployment Stack deployment with deny-settings, validation, and cutover.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[708,709,710,713],{"name":11,"slug":8,"type":16},{"name":618,"slug":619,"type":16},{"name":711,"slug":712,"type":16},"Infrastructure as Code","infrastructure-as-code",{"name":714,"slug":715,"type":16},"Migration","migration",261,"https:\u002F\u002Fgithub.com\u002FAzure\u002Fazure-blueprints","2026-08-20T03:28:18.136156",{"slug":599,"name":599,"fn":600,"description":601,"org":720,"tags":721,"stars":24,"repoUrl":25,"updatedAt":609},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[722,723,724],{"name":11,"slug":8,"type":16},{"name":606,"slug":607,"type":16},{"name":22,"slug":23,"type":16},{"slug":611,"name":611,"fn":612,"description":613,"org":726,"tags":727,"stars":24,"repoUrl":25,"updatedAt":624},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[728,729,730,731],{"name":11,"slug":8,"type":16},{"name":618,"slug":619,"type":16},{"name":621,"slug":622,"type":16},{"name":22,"slug":23,"type":16},{"slug":138,"name":138,"fn":626,"description":627,"org":733,"tags":734,"stars":24,"repoUrl":25,"updatedAt":637},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[735,736,737,738,739],{"name":11,"slug":8,"type":16},{"name":19,"slug":20,"type":16},{"name":14,"slug":15,"type":16},{"name":22,"slug":23,"type":16},{"name":635,"slug":636,"type":16},{"slug":4,"name":4,"fn":5,"description":6,"org":741,"tags":742,"stars":24,"repoUrl":25,"updatedAt":26},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[743,744,745,746],{"name":11,"slug":8,"type":16},{"name":19,"slug":20,"type":16},{"name":14,"slug":15,"type":16},{"name":22,"slug":23,"type":16},{"slug":113,"name":113,"fn":646,"description":647,"org":748,"tags":749,"stars":24,"repoUrl":25,"updatedAt":656},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[750,751,752,753],{"name":651,"slug":652,"type":16},{"name":11,"slug":8,"type":16},{"name":621,"slug":622,"type":16},{"name":22,"slug":23,"type":16},{"slug":658,"name":658,"fn":659,"description":660,"org":755,"tags":756,"stars":24,"repoUrl":25,"updatedAt":666},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[757,758,759],{"name":11,"slug":8,"type":16},{"name":14,"slug":15,"type":16},{"name":22,"slug":23,"type":16},{"slug":668,"name":668,"fn":669,"description":670,"org":761,"tags":762,"stars":24,"repoUrl":25,"updatedAt":679},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[763,764,765,766],{"name":11,"slug":8,"type":16},{"name":19,"slug":20,"type":16},{"name":22,"slug":23,"type":16},{"name":677,"slug":678,"type":16},{"slug":768,"name":768,"fn":769,"description":770,"org":771,"tags":772,"stars":24,"repoUrl":25,"updatedAt":779},"sdaf-orientation-and-surface","orient users to SDAF architecture","Orient a newcomer to the SAP Deployment Automation Framework (SDAF): explain the spine (control plane → workload zone → SAP system → software → install → operate\u002Fremove), summarise the three execution surfaces (Local, Azure DevOps, GitHub Actions), and print the install command for the matching surface bootstrap plugin — as documented in this repository's `docs\u002FPLUGINS.md` — so the operator can run it manually. Use when a user says \"what is SDAF\", \"how is SDAF structured\", \"where do I start with SDAF\", \"which surface should I use\", \"SDAF Local vs ADO vs GitHub\", \"workstation vs Azure Pipelines vs GitHub workflows\", \"how do I install the SDAF ADO\u002FGitHub plugin\", or \"I'm new to SDAF\". Do NOT use for readiness pre-flight (see sdaf-readiness-check), workspace\u002Ftfvars layout (see sdaf-workspace-and-tfvars), or troubleshooting a failed run (see sdaf-failure-triage).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[773,774,775,778],{"name":651,"slug":652,"type":16},{"name":11,"slug":8,"type":16},{"name":776,"slug":777,"type":16},"Documentation","documentation",{"name":22,"slug":23,"type":16},"2026-09-02T07:46:52.116557",{"slug":781,"name":781,"fn":782,"description":783,"org":784,"tags":785,"stars":24,"repoUrl":25,"updatedAt":799},"sdaf-plan-and-test-semantics","manage SDAF plan and test semantics","Explain SDAF plan-only \u002F test \u002F apply semantics without pretending they are universal. Compares the documented Local commands, Azure DevOps wrapper pipelines, and GitHub Actions workflows for control plane, workload zone, and SAP system: local stage commands show Terraform plans and then apply after approval; ADO\u002FGitHub workload-zone and SAP-system test runs stop after the plan; the current hosted control-plane test options do not provide a plan-only run. Use when a user says \"what does test do in SDAF\", \"is this a real dry run\", \"plan-only vs apply\", \"workflow 01 dry-run\", \"pipeline 02 test\", or \"TEST_ONLY\". Do NOT use to actually deploy a stage or to triage a failed run (see sdaf-control-plane-bootstrap \u002F sdaf-workload-zone \u002F sdaf-sap-system \u002F sdaf-failure-triage).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[786,789,790,793,796],{"name":787,"slug":788,"type":16},"Automation","automation",{"name":11,"slug":8,"type":16},{"name":791,"slug":792,"type":16},"Azure DevOps","azure-devops",{"name":794,"slug":795,"type":16},"CI\u002FCD","ci-cd",{"name":797,"slug":798,"type":16},"GitHub Actions","github-actions","2026-09-02T07:48:08.951811",{"slug":126,"name":126,"fn":801,"description":802,"org":803,"tags":804,"stars":24,"repoUrl":25,"updatedAt":811},"validate deployed SDAF SAP systems","Validate a deployed SDAF SAP system through the SDAF-owned QA entry points: the local quality-assurance menu and the documented Azure DevOps pipeline 13 path. Choose configuration checks vs functional tests, apply `TEST_GROUPS` \u002F `TEST_CASES` safely, interpret `quality_assurance\u002F` and `logs\u002F`, and enforce the documented boundary that the GitHub Actions wrapper is still pending. Use when a user says \"run quality assurance\", \"run configuration checks\", \"pipeline 13 QA\", \"offline HA validation\", or \"why does the report say No test results found\". Do NOT use to deploy the SAP system or generate `sap-parameters.yaml` \u002F `\u003CSID>_hosts.yaml` (see `sdaf-sap-system`), or for a generic failed-run report with no QA-stage context (see `sdaf-failure-triage`).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[805,806,807,810],{"name":787,"slug":788,"type":16},{"name":11,"slug":8,"type":16},{"name":808,"slug":809,"type":16},"Quality Assurance","quality-assurance",{"name":22,"slug":23,"type":16},"2026-09-02T07:46:49.932123",145]