azure-prepare

Generates Azure infrastructure code, azure.yaml, and Dockerfiles through a plan-first deployment preparation workflow.

1|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/AlahmadiQ8/sre-agent-demo --skill azure-prepare-alahmadiq8
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: azure-prepare
Source: https://github.com/AlahmadiQ8/sre-agent-demo/tree/main/.claude/skills/azure-prepare
Command: npx skills add https://github.com/AlahmadiQ8/sre-agent-demo --skill azure-prepare-alahmadiq8

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Preparing an application for Azure deployment requires choosing the right hosting services, writing correct Bicep or Terraform infrastructure, configuring azd, and validating quotas — a process prone to misconfiguration and deployment failures. This Skill enforces a structured plan-first workflow that produces reviewed, validated deployment artifacts. ## Core Features & Use Cases - Plan-First Workflow: Creates a mandatory .azure/plan.md capturing requirements, architecture, recipe selection, and quota validation before any code is generated. - Multi-Recipe Infrastructure Generation: Produces Bicep, Terraform, AZD, or Azure CLI artifacts including azure.yaml, infra/ modules, and Dockerfiles, with special handling for .NET Aspire and Azure Functions projects. - Quota and Region Validation: Confirms subscription and location with the user, checks region availability, and validates provisioning limits via the azure-quotas skill before generation. - Use Case: A developer asks to deploy a containerized Node.js API to Azure Container Apps. The Skill analyzes the workspace, drafts a plan with service mappings and quota checks, gets approval, then generates the Bicep modules and Dockerfile before handing off to azure-validate and azure-deploy. ## Quick Start Ask the assistant to prepare your application for deployment to Azure Container Apps and it will create a plan for your approval before generating the infrastructure files.

Frequently Asked Questions about azure-prepare

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prepare my application for Azure deployment?

Invoke the azure-prepare workflow, which analyzes your workspace, gathers requirements, and creates a .azure/plan.md for approval. After approval it generates infrastructure files, azure.yaml, and Dockerfiles, then hands off to azure-validate and azure-deploy.

Should I use Bicep or Terraform for Azure infrastructure?

Default to AZD with Bicep for new projects and simplest deployment via azd up. Choose AZD with Terraform when Terraform is requested, and pure Terraform only for multi-cloud deployments or complex existing Terraform workflows.

Does azure-prepare support .NET Aspire projects?

Yes, Aspire projects are detected via AppHost.csproj files and must use azd init --from-code with an environment name flag. Manually creating azure.yaml or infra files for Aspire causes deployment failures.

Does this skill deploy resources to Azure?

No, it only generates infrastructure code and configuration files. Deployment execution such as azd up or terraform apply is handled by the separate azure-deploy skill after azure-validate runs.

Why does azd init fail in non-interactive environments?

azd init fails without the -e environment-name flag when no TTY is available, such as in agents or CI pipelines. Always run azd init --from-code -e <name> and then set AZURE_SUBSCRIPTION_ID and AZURE_LOCATION immediately.

When should I use azure-cloud-migrate instead of azure-prepare?

Use azure-cloud-migrate for cross-cloud migrations such as moving AWS Lambda or GCP workloads to Azure. Use azure-prepare for creating new apps, modernizing on-premises applications, or adding components to existing Azure projects.