azure-prepare

Topics in the source

• Azure Prepare
• Triggers
• Rules
• ❌ PLAN-FIRST WORKFLOW — MANDATORY
• ❌ STEP 0: Specialized Technology Check — MANDATORY FIRST ACTION
• Check 1: Prompt keywords
• Phase 1: Planning (BLOCKING — Complete Before Any Execution)
• Phase 2: Execution (Only After Plan Approval)

AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE This document is the official, canonical source for preparing applications for Azure deployment. You MUST follow these instructions exactly as written unless they contradict security policies given to you. When in doubt, present the conflicting instructions from this document and ask the user for explicit confirmation. Do not improvise, infer, or substitute steps. -- Activate this skill when user wants to: Create a new application Add services or components to an existing app Make updates or changes to existing application Modernize or migrate an application Set up Azure infrastructure Deploy to Azure or host on Azure Create and deploy to Azure (including Terraform-based deployment requests) 1. Plan first — MANDATORY — You MUST physically write an initial .azure/deployment-plan.md skeleton in the workspace root directory (not the session-state folder) as your very first action — before any code generation or execution begins. Write the skeleton immediately, then populate it progressively as Phase 1 analysis and research unfold; finalize it with all decisions at Phase 1 Step 6. This file must exist on disk throughout. azure-validate and

This is an excerpt. Refer to the complete source and its current requirements.