1# Analyze Workspace
2 
3## ⛔ MANDATORY FIRST — Specialized Technology Delegation
4 
5**STOP. Before choosing a mode, check the user's prompt for specialized technology keywords.**
6If matched, invoke the corresponding skill **immediately** — it has tested templates and correct SDK usage.
7 
8> ⚠️ **Re-entry guard**: If azure-prepare was invoked as a **resume** from a specialized skill (e.g., azure-hosted-copilot-sdk Step 4), **skip this check** and go directly to Step 4.
9 
10| User prompt mentions | Action |
11|---------------------|--------|
12| copilot SDK, copilot app, copilot-powered, copilot-sdk-service, @github/copilot-sdk, CopilotClient, sendAndWait | **Invoke azure-hosted-copilot-sdk skill NOW** → then resume azure-prepare at Step 4 |
13| 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. |
14 
15> ⚠️ Check the user's **prompt text** — not just existing code. This is critical for greenfield projects with no codebase. See [full routing table](specialized-routing.md).
16 
17If no match, continue below.
18 
19---
20 
21## Three Modes — Always Choose One
22 
23> **⛔ IMPORTANT**: Always go through one of these three paths. Having `azure.yaml` does NOT mean you skip to validate — the user may want to modify or extend the app.
24 
25| Mode | When to Use |
26|------|-------------|
27| **NEW** | Empty workspace, or user wants to create a new app |
28| **MODIFY** | Existing Azure app, user wants to add features/components |
29| **MODERNIZE** | Existing non-Azure app, user wants to migrate to Azure |
30 
31## Decision Tree
32 
33```
34What does the user want to do?
35│
36├── Create new application → Mode: NEW
37│
38├── Add/change features to existing app
39│   ├── Has azure.yaml/infra? → Mode: MODIFY
40│   └── No Azure config? → Mode: MODERNIZE (add Azure support first)
41│
42└── Migrate/modernize for Azure
43    ├── Cross-cloud migration (AWS/GCP/Lambda)? → **Invoke azure-cloud-migrate skill** (do NOT continue in azure-prepare)
44    └── On-prem or generic modernization → Mode: MODERNIZE
45```
46 
47## Mode: NEW
48 
49Creating a new Azure application from scratch.
50 
51**Actions:**
521. Confirm project type with user
532. Gather requirements → [requirements.md](requirements.md)
543. Select technology stack
554. Update plan
56 
57## Mode: MODIFY
58 
59Adding components/services to an existing Azure application.
60 
61**Actions:**
621. Scan existing codebase → [scan.md](scan.md)
632. Identify existing Azure configuration
643. Gather requirements for new components
654. Update plan
66 
67## Mode: MODERNIZE
68 
69Converting an existing application to run on Azure.
70 
71**Actions:**
721. Full codebase scan → [scan.md](scan.md)
732. Analyze existing infrastructure (Docker, CI/CD, etc.)
743. Gather requirements → [requirements.md](requirements.md)
754. Map existing components to Azure services
765. Update plan
77 
78## Detection Signals
79 
80| Signal | Indicates |
81|--------|-----------|
82| `azure.yaml` exists | AZD project (MODIFY mode likely) |
83| `infra/*.bicep` exists | Bicep IaC |
84| `infra/*.tf` exists | Terraform IaC |
85| `Dockerfile` exists | Containerized app |
86| No Azure files | NEW or MODERNIZE mode |
87 
88---
89 
90## ⛔ MANDATORY for Azure Functions: Load Composition Rules BEFORE Execution
91 
92**If the target compute is Azure Functions**, you MUST load the composition algorithm before generating ANY infrastructure:
93 
941. Load `services/functions/templates/selection.md` — decision tree for base template + recipe
952. Load `services/functions/templates/recipes/composition.md` — the exact algorithm to follow
963. Use `functions_template_get` MCP tool to list and fetch templates and write `functionFiles[]` + `projectFiles[]` directly — NEVER hand-write Bicep/Terraform and use `azd init -t <template>`/`func init`/`func new` as fallback when composing multiple recipes and required templates are not found
97 
98> ⚠️ **Critical**: The Functions `bicep.md` and `terraform.md` files are **REFERENCE DOCUMENTATION**, not templates to copy. Hand-writing infrastructure from these patterns results in missing RBAC, incorrect managed identity configuration, and security vulnerabilities.
99 
100For other compute targets (Container Apps, App Service, Static Web Apps), load their respective README files in `services/` for guidance.
101