azure-prepare

Create Azure infrastructure plans and generate Bicep or Terraform preparation artifacts.

Updated Dec 20, 2023
One-click install
npx skills add https://github.com/Thiago-Cruz-eng/Hibrygame --skill azure-prepare-thiago-cruz-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: azure-prepare
Source: https://github.com/Thiago-Cruz-eng/Hibrygame/tree/main/.claude/skills/azure-prepare
Command: npx skills add https://github.com/Thiago-Cruz-eng/Hibrygame --skill azure-prepare-thiago-cruz-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill turns your application intent (new app, added services, modernization updates) into a validated, Azure-ready infrastructure and configuration plan, so deployments can proceed reliably without mixing preparation and execution responsibilities.

Core Features & Use Cases

  • Plan-first Azure preparation: creates and progressively updates .azure/plan.md before any artifacts are generated.
  • Recipe-driven Azure infrastructure generation: supports AZD (Bicep default, or Terraform), AZ CLI, and standalone Bicep/Terraform workflows with architecture-to-service mapping.
  • Azure-safe workflow orchestration: enforces quota/resource-capacity checks, confirms Azure subscription and location, and requires validation handoff to azure-validate before deployment.
  • Specialized routing for Azure Functions/Durable and other known technologies: triggers dedicated guidance when the prompt indicates a technology with tested templates (e.g., azure-cloud-migrate, azure-hosted-copilot-sdk).

Quick Start

Use the azure-prepare skill to prepare infrastructure by asking: "Prepare my application for deployment to Azure using Terraform and deploy it after validation."

Frequently Asked Questions about azure-prepare

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

FAQPage Schema
How do I prepare Azure application infrastructure before deployment?

To prepare Azure application infrastructure, you must generate a mandatory plan-first artifact (.azure/plan.md) that validates quotas and confirms subscription details before outputting IaC files like Bicep or Terraform for deployment workflows.

Can I use Terraform instead of Bicep for Azure deployment planning?

Yes, Azure deployment planning supports Terraform alongside Bicep. The workflow generates the required IaC and environment files based on your chosen tool, applying architecture-to-service mapping and security hardening guidance for either format.

What is a plan-first artifact in Azure infrastructure as code?

A plan-first artifact (.azure/plan.md) is a mandatory file created before generating any IaC. It enforces strict workflow control by tracking plan status progression to Ready for Validation and ensuring subscription and quota validation before deployment execution.

How do I validate Azure quota and resource capacity before generating Bicep files?

Azure quota and resource capacity validation occurs during the preparation phase. The workflow enforces these checks alongside subscription and location confirmation, updating the plan status to Ready for Validation before handing off to validation steps.

Does Azure deployment planning support Azure Functions and Durable Functions?

Yes, Azure deployment planning includes specialized routing for Azure Functions and Durable Functions. It triggers dedicated guidance and tested templates when your prompt indicates these specific technologies for infrastructure generation.

Why does my Azure IaC workflow require a validation handoff before deployment?

Azure IaC workflows require a validation handoff to azure-validate to separate preparation from execution responsibilities. This strict workflow control ensures all generated Bicep or Terraform artifacts are fully validated before any deployment step occurs.