azure-adr
**ANALYSIS SKILL** — Creates Azure Architecture Decision Records (ADRs) with WAF pillar mapping, alternatives, and consequences. WHEN: "create ADR", "document decision", "architecture decision record", "record why we chose", "WAF pillar justification", "trade-off analysis". DO NOT USE FOR: IaC code (06b/06t agents), architecture diagrams (drawio), cost estimates (cost-estimate-subagent).
git clone --depth 1 https://github.com/jonathan-vella/apex /tmp/azure-adr && cp -r /tmp/azure-adr/.github/skills/azure-adr ~/.claude/skills/azure-adrSKILL.md
# Azure Architecture Decision Records (ADR) Skill
Create formal Architecture Decision Records that document significant
infrastructure decisions with Azure-specific context, WAF pillar analysis,
and implementation guidance.
## Output Naming
ADRs are saved to `agent-output/{project}/` with one of two phase prefixes:
| Phase | Prefix | Status default | Trigger |
| ------------------ | --------------- | -------------- | -------------------------------------------- |
| Step 3 (Design) | `03-des-adr-` | `Proposed` | Architect agent, design/planning language |
| Step 7 (As-Built) | `07-ab-adr-` | `Accepted` | After deploy, implemented/current-state language |
Full filename: `{prefix}NNNN-{kebab-title}.md` (e.g.,
`03-des-adr-0001-use-cosmos-db-for-state.md`). NNNN is 4-digit sequential
per project.
The `07-ab-adr-` ADR may differ from `03-des-adr-` if implementation
required changes — document deviations in the "Implementation Notes"
section.
## Rules
1. **One decision per ADR** — keep ADRs focused on a single decision
2. **Include alternatives** — always document at least 2-3 considered and rejected
3. **Map to WAF pillars** — show impact on each of the 5 Well-Architected pillars
4. **Link to requirements** — reference the requirement that drove the decision
5. **Keep it concise** — ADRs should be readable in 5 minutes
6. **Document both consequences** — at least 1 positive and 1 negative
## Steps
1. **Gather context** — decision context, alternatives, stakeholders
2. **Determine number** — check existing ADRs in `agent-output/{project}/` for next sequence
3. **Determine phase** — design (`03-des-`) or as-built (`07-ab-`)
4. **Generate document** — follow [`references/adr-template.md`](references/adr-template.md)
5. **Include WAF analysis** — map decision impact to all 5 pillars
6. **Document alternatives** — list 2-3 with rejection reasons
7. **Self-check** — run through [`references/quality-checklist.md`](references/quality-checklist.md)
## Reference Index
Load on demand:
| Reference | When to Load |
| ---------------------------------- | ----------------------------------------------------- |
| `references/adr-template.md` | Authoring the ADR (full template with all sections) |
| `references/example-prompts.md` | Looking for trigger phrasing / common ADR topics |
| `references/quality-checklist.md` | Final self-check before saving |
| `references/guardrails.md` | DO/DON'T rules, anti-pattern table |Guidance for instrumenting webapps with Azure Application Insights. Provides telemetry patterns, SDK setup, and configuration references. WHEN: how to instrument app, App Insights SDK, telemetry patterns, what is App Insights, Application Insights guidance, instrumentation examples, APM best practices.
Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.
Configure Azure API Management as an AI Gateway for AI models, MCP tools, and agents. WHEN: semantic caching, token limit, content safety, load balancing, AI model governance, MCP rate limiting, jailbreak detection, add Azure OpenAI backend, add AI Foundry model, test AI gateway, LLM policies, configure AI backend, token metrics, AI cost control, convert API to MCP, import OpenAPI to gateway.
ROUTING SKILL — delegates to specialized diagram skills. USE FOR: any diagram request when the caller does not know which tool to use. Routes to drawio, python-diagrams, or mermaid based on diagram type.
Build and deploy GitHub Copilot SDK apps to Azure. WHEN: build copilot app, create copilot app, copilot SDK, @github/copilot-sdk, scaffold copilot project, copilot-powered app, deploy copilot app, host on azure, azure model, BYOM, bring your own model, use my own model, azure openai model, DefaultAzureCredential, self-hosted model, copilot SDK service, chat app with copilot, copilot-sdk-service template, azd init copilot, CopilotClient, createSession, sendAndWait, GitHub Models API.
Troubleshoot and resolve issues with Azure Messaging SDKs for Event Hubs and Service Bus. Covers connection failures, authentication errors, message processing issues, and SDK configuration problems. WHEN: event hub SDK error, service bus SDK issue, messaging connection failure, AMQP error, event processor host issue, message lock lost, send timeout, receiver disconnected, SDK troubleshooting, azure messaging SDK, event hub consumer, service bus queue issue, topic subscription error, enable logging event hub, service bus logging, eventhub python, servicebus java, eventhub javascript, servicebus dotnet, event hub checkpoint, event hub not receiving messages, service bus dead letter.
Authoritative reference for VS Code Copilot customization mechanisms: instructions, prompt files, custom agents, agent skills, MCP servers, hooks, and plugins. Use when deciding which customization type to use, creating new .instructions.md/.prompt.md/.agent.md/SKILL.md/mcp.json files from scratch, or debugging why a customization is not loading. DO NOT USE FOR: routine file edits where the format is already known.
Provides canonical entity counts from count-manifest.json. Use when agents need to reference how many agents, skills, instructions, or validators exist. Prevents hard-coded counts. WHEN: agent count, skill count, how many agents, how many skills, entity inventory, project statistics.