Analyze Workspace
⛔ MANDATORY FIRST — Specialized Technology Delegation
STOP. Before choosing a mode, check the user's prompt for specialized technology keywords. If matched, invoke the corresponding skill immediately — it has tested templates and correct SDK usage.
⚠️ Re-entry guard: If azure-prepare was invoked as a resume from a specialized skill, skip this check and go directly to Step 4.
| User prompt mentions | Action |
|---|---|
| Azure Functions, function app, serverless function, timer trigger, func new | Stay in azure-prepare. When selecting compute, prefer Azure Functions templates and best practices, then continue from Step 4. |
⚠️ Check the user's prompt text — not just existing code. This is critical for greenfield projects with no codebase. See full routing table.
If no match, continue below.
Three Modes — Always Choose One
⛔ IMPORTANT: Always go through one of these three paths. Having
azure.yamldoes NOT mean you skip to validate — the user may want to modify or extend the app.
| Mode | When to Use |
|---|---|
| NEW | Empty workspace, or user wants to create a new app |
| MODIFY | Existing Azure app, user wants to add features/components |
| MODERNIZE | Existing non-Azure app, user wants to migrate to Azure |
Decision Tree
What does the user want to do?
│
├── Create new application → Mode: NEW
│
├── Add/change features to existing app
│ ├── Has azure.yaml/infra? → Mode: MODIFY
│ └── No Azure config? → Mode: MODERNIZE (add Azure support first)
│
└── Migrate/modernize for Azure
├── Cross-cloud migration (AWS/GCP/Lambda)? → **Invoke azure-cloud-migrate skill** (do NOT continue in azure-prepare)
└── On-prem or generic modernization → Mode: MODERNIZEMode: NEW
Creating a new Azure application from scratch.
Actions:
- Confirm project type with user
- Gather requirements → requirements.md
- Select technology stack
- Update plan
Mode: MODIFY
Adding components/services to an existing Azure application.
Actions:
- Scan existing codebase → scan.md
- Identify existing Azure configuration
- Gather requirements for new components
- Update plan
Mode: MODERNIZE
Converting an existing application to run on Azure.
Actions:
- Full codebase scan → scan.md
- Analyze existing infrastructure (Docker, CI/CD, etc.)
- Gather requirements → requirements.md
- Map existing components to Azure services
- Update plan
Detection Signals
| Signal | Indicates |
|---|---|
azure.yaml exists |
AZD project (MODIFY mode likely) |
infra/*.bicep exists |
Bicep IaC |
infra/*.tf exists |
Terraform IaC |
Dockerfile exists |
Containerized app |
| No Azure files | NEW or MODERNIZE mode |
⛔ MANDATORY for Azure Functions: Load Composition Rules BEFORE Execution
If the target compute is Azure Functions, you MUST load the composition algorithm before generating ANY infrastructure:
- Load
services/functions/templates/selection.md— decision tree for base template + recipe - Load
services/functions/templates/recipes/composition.md— the exact algorithm to follow - Use
functions_template_getMCP tool to list and fetch templates and writefunctionFiles[]+projectFiles[]directly — NEVER hand-write Bicep/Terraform and useazd init -t <template>/func init/func newas fallback when composing multiple recipes and required templates are not found
⚠️ Critical: The Functions
bicep.mdandterraform.mdfiles are REFERENCE DOCUMENTATION, not templates to copy. Hand-writing infrastructure from these patterns results in missing RBAC, incorrect managed identity configuration, and security vulnerabilities.
For other compute targets (Container Apps, App Service, Static Web Apps), load their respective README files in services/ for guidance.