ohorizons-lastest

Observability stack — deploy Prometheus, Grafana, Loki, and Alertmanager, plus day-2 monitoring operations. USE FOR: deploy Prometheus, configure Grafana, setup Loki, Alertmanager rules, monitoring dashboards, observability troubleshooting. DO NOT USE FOR: application logging code, Terraform IaC (use terraform-cli), CI/CD pipelines (use deploy-orchestration).

Deploys the upstream open-source Backstage developer portal on Azure AKS or locally via Docker Desktop. USE FOR: deploy Backstage, Backstage on AKS, Backstage local Docker, Backstage Helm chart, Backstage PostgreSQL, Backstage ACR image, Backstage GitHub OAuth, Microsoft Entra ID auth, GitHub Enterprise Managed Users. DO NOT USE FOR: full platform orchestration (use deploy-orchestration), Azure infrastructure provisioning (use @azure-portal-deploy).

End-to-end platform deployment orchestration — prerequisites, Terraform, Kubernetes verification, and troubleshooting. USE FOR: full platform deployment, deployment sequence, prerequisite validation, post-deploy verification, deployment troubleshooting. DO NOT USE FOR: Terraform modules (use terraform-cli), Kubernetes read operations (use kubectl-cli), Helm package operations (use helm-cli).

GitHub CLI operations for repository and workflow management. USE FOR: gh repo, gh pr, gh issue, gh workflow, GitHub API, repository management, pull request automation. DO NOT USE FOR: Azure DevOps (use @ado-integration), Terraform (use terraform-cli), Kubernetes (use kubectl-cli).

Access 79 tools across 17 modules from the local MCP Ecosystem server to fetch live methodology, templates, components, and complete OFFICIAL DOCUMENTATION for spec-kit, anthropics-skills, agent-framework, gh-aw, agents-md, github-copilot-docs, the five Backstage modules, plus full official docs: Microsoft Learn (federated — all of Azure/AKS/AI Foundry/CAF/WAF), VS Code, GitHub (docs.github.com), Anthropic/Claude, Azure Cloud Adoption Framework (CAF) and Well-Architected Framework (WAF). USE FOR: Spec-Driven Development phases and commands, Microsoft Agent Framework patterns, GitHub Agentic Workflows (gh-aw), AGENTS.md format and section templates, GitHub Copilot documentation and customization, Anthropic docs, Backstage documentation, Software Catalog, Software Templates, plugin directory, Backstage UI and Storybook, searching all of Microsoft Learn (Azure, AKS, AI Foundry, CAF, WAF), VS Code docs, GitHub docs (Actions, GHAS, OIDC, Packages), and the Claude developer docs — to support agents during the whole

Produce complete, professional architecture diagrams that use the official Azure, Microsoft, and GitHub (Octicons) icon sets, output as editable draw.io (.drawio) files and exported SVG. Covers the official icon catalogs and their terms of use, the draw.io mxGraph file format, layout and connector conventions, and a bundled draw.io MCP server (Python FastMCP) that creates and edits .drawio diagrams programmatically (add nodes with official icons, connect edges, group, and lay out). Use whenever the deliverable includes an architecture diagram, a system context, a component or deployment diagram, or any cloud diagram that must use official vendor icons. Pairs with ai-native-engineer and agentic-architecture-patterns, and complements svg-professional for hand-crafted SVG.

Azure CLI operations for cloud resource management. USE FOR: az login, az aks, az acr, az keyvault, Azure resource provisioning, Azure resource group, Azure subscription management. DO NOT USE FOR: Terraform IaC (use terraform-cli), Kubernetes operations (use kubectl-cli), Helm charts (use helm-cli).

Azure infrastructure patterns and best practices. USE FOR: Azure architecture patterns, hub-spoke networking, private endpoints, Workload Identity, resource naming, tagging strategy. DO NOT USE FOR: Terraform CLI commands (use terraform-cli), Azure CLI commands (use azure-cli), Kubernetes operations (use kubectl-cli).

CLI tool prerequisites validation and setup. USE FOR: validate prerequisites, check CLI tools, install missing tools, verify versions, prerequisite checklist. DO NOT USE FOR: deployment orchestration (use deploy-orchestration), Terraform operations (use terraform-cli), Kubernetes operations (use kubectl-cli).

Validation scripts for deployment and configuration verification. USE FOR: validate deployment, validate configuration, validate prerequisites, run validation scripts, post-deploy checks. DO NOT USE FOR: Terraform validation (use terraform-cli), Kubernetes checks (use kubectl-cli), Helm operations (use helm-cli).

ArgoCD CLI operations for GitOps workflows — installation, bootstrap, and day-2 management. USE FOR: ArgoCD install, ArgoCD bootstrap, GitOps sync, ArgoCD app create, ArgoCD troubleshoot, ApplicationSet. DO NOT USE FOR: Helm chart management (use helm-cli), kubectl operations (use kubectl-cli), full platform deployment orchestration (use deploy-orchestration).

Validate an architecture document (the {app}_Architecture.md produced by the Senior Cloud Architect agent) against a hard Definition of Done: required sections, the five required diagrams, well-formed Mermaid, the seven explanation parts per diagram, and the repository copy conventions. Use when producing, reviewing, or finishing an architecture document, or whenever you need to confirm a Mermaid-based architecture deliverable is complete and will render before presenting it.

Creates professional Markdown documents with YAML frontmatter, versioning, author attribution, table of contents, and consistent formatting. Use for Markdown documents, README, ADR, spec, guide, changelog, runbook, RFC, technical docs, and converting PPTX or PowerPoint files to narrative Markdown reading editions with markitdown. Trigger on 'md file', 'markdown', '.md', 'documento markdown', 'criar um readme', 'escrever documentação', 'write a spec', 'draft a guide', 'convert PPTX to Markdown', 'extract PPTX', or 'PowerPoint to Markdown'. Do not use for creating PPTX presentations, Word documents, diagrams, or PDFs.

Azure AI Foundry — provisioning, model deployment, RAG configuration, and operational management. USE FOR: provision AI Foundry, deploy AI model, configure RAG, AI Foundry operations, OpenAI model deployment, AI workspace setup. DO NOT USE FOR: general Azure infrastructure (use azure-infrastructure), Terraform IaC (use terraform-cli), Kubernetes operations (use kubectl-cli).

Configures GitHub Codespaces dev environments for each Golden Path template type so developers get a fully ready workspace when scaffolding from the portal. USE FOR: devcontainer.json configuration, Codespaces setup, Golden Path dev environment, container features, SDK pre-installation. DO NOT USE FOR: Backstage deployment (use backstage-deployment), CI/CD pipelines (use deploy-orchestration), template creation (use backstage-deployment).

Database operations and health monitoring. USE FOR: PostgreSQL health check, database backup, database restore, connection string, database migration, database monitoring. DO NOT USE FOR: Azure infrastructure provisioning (use azure-cli), Terraform IaC (use terraform-cli), full platform deployment (use deploy-orchestration).

Helm CLI operations for Kubernetes package management. USE FOR: helm install, helm upgrade, helm rollback, Helm chart management, Helm values, Helm repo add. DO NOT USE FOR: kubectl operations (use kubectl-cli), ArgoCD sync (use argocd-cli), Terraform IaC (use terraform-cli).

GitHub Issue-driven operations dispatcher — maps slash commands in issue comments to automation scripts. USE FOR: slash command dispatch, issue ops automation, /onboard command, /validate command, /check-agents command, IssueOps workflow. DO NOT USE FOR: manual script execution (use validation-scripts), Backstage deployment (use backstage-deployment), full platform deployment (use deploy-orchestration).

Kubernetes CLI operations for AKS cluster management. USE FOR: kubectl get, kubectl apply, kubectl describe, pod troubleshooting, service debugging, namespace management. DO NOT USE FOR: Helm charts (use helm-cli), ArgoCD sync (use argocd-cli), Azure resource provisioning (use azure-cli).

GitHub Actions CI/CD diagnostics — workflow run analysis, job/step failure identification, and remediation patterns. USE FOR: diagnose pipeline, workflow failure, build error, deploy failure, GitHub Actions troubleshooting, CI/CD debug. DO NOT USE FOR: test analysis (use test-coverage), Kubernetes operations (use kubectl-cli), Helm charts (use helm-cli).

INVEST user story decomposition and GitHub Issues creation — epic analysis, persona identification, acceptance criteria, and sprint-ready stories. USE FOR: decompose epic, create user stories, INVEST criteria, acceptance criteria, sprint planning, create GitHub issues, story mapping, backlog grooming. DO NOT USE FOR: test analysis (use test-coverage), pipeline diagnostics (use pipeline-diagnostics), Azure infrastructure design (use azure-infrastructure).

Terraform CLI operations for Azure infrastructure management. USE FOR: terraform init, terraform plan, terraform apply, terraform destroy, state management, module development, tfsec scanning. DO NOT USE FOR: Azure CLI operations (use azure-cli), Kubernetes operations (use kubectl-cli), Helm charts (use helm-cli).

Test coverage and quality gate analysis — CI check runs, PR review status, coverage reports, and test improvement recommendations. USE FOR: check runs analysis, test coverage, PR checks, quality gate, test failures, coverage diff, failing checks, test quality. DO NOT USE FOR: pipeline diagnostics (use pipeline-diagnostics), security review (use @security), deployment orchestration (use @deploy).

Spec-Driven Development orchestrator, the open-source alternative to AWS Kiro. Transforms natural language into production-grade specs through interactive discovery. Auto-scans codebases, generates EARS-notation requirements, creates Mermaid architecture diagrams, produces sequenced task plans with [P] parallel markers and pre-implementation gates, runs quality gates with traceability matrices, and hands off to coding agents. Works in GitHub Copilot custom agents, prompt files, and skills. USE THIS when the user mentions: spec, requirements, plan feature, user stories, acceptance criteria, technical design, architect solution, implementation plan, SDD, "spec this", "plan this", "break into tasks", PRD, constitution, "like Kiro", bugfix spec, quality gate, spec sync, or any variation of spec-driven development.