// Use when implementation exists and needs to be exercised locally against provisioned Azure dependencies, before deploying.
Create Azure architecture diagrams, flowcharts, data-flow visualizations, or illustrations as Excalidraw documents with embedded official Azure service icons, and export them as SVG and PNG. Use whenever the user wants to draw, sketch, diagram, visualize, or illustrate an Azure workload, solution, reference architecture, network topology, AI/ML topology, or any cloud system involving Azure services — even if they don't say "Excalidraw". Triggers include: "diagram", "architecture diagram", "draw", "sketch", "visualize", "flowchart", "data flow", "topology", "illustrate" combined with any Azure / cloud context. Also use to re-render existing `.excalidraw` files to SVG/PNG.
Use when local verification passed and the feature is ready to ship to Azure.
Use when a plan exists and the application source or IaC needs to be created or updated.
Use when a spec exists and an implementation or Azure deployment plan is needed, before writing code.
Use when the user wants to run the full Specify → Plan → Implement → Deploy loop end-to-end in one shot. Accepts a free-form prompt that is passed to specify.
Use when starting or refining a project's requirements, before any planning or coding. Supports sub-commands `sync`, `reverse`, and `validate`.
| name | verify |
| description | Use when implementation exists and needs to be exercised locally against provisioned Azure dependencies, before deploying. |
Requires spec.md. If spec.md is missing, auto-run specify with the user's prompt, then auto-run plan and implement. If plan.md is missing, auto-run plan and implement. If implementation.md is missing, auto-run implement first. If ./src/ is missing, return to Implement. Load workspace context per copilot-instructions.md.
azd provision and wait for completion:
azd provision -e <AZD environment>
.env, local.settings.json, appsettings.Development.json, …) using azd env get-values -e <AZD environment>. Show the user which keys are written (names only). Secrets must resolve via Key Vault references / managed identity — never as literals../docs/verify.md with process, results, and manual test instructions. On resume, re-read ./docs/verify.md and re-run only the checks not yet marked passed.
dotnet run apphost.cs).Pause if: provisioning fails, a local component fails to start, or a test fails — report and wait, do not retry blindly.
Do not claim verification passed without ensuring that the local servers started successfully in this turn and reporting exit code + key output. Summarize the updated ./docs/verify.md, and prompt the user to continue with deploy.