// Use when a spec exists and an implementation or Azure deployment plan is needed, before writing code.
| name | plan |
| description | Use when a spec exists and an implementation or Azure deployment plan is needed, before writing code. |
Requires spec.md. Load workspace context per copilot-instructions.md.
Cycle these phases as needed (iterative, not linear). For highly ambiguous tasks, do only Discovery, then Alignment, before Design.
./src/ or ./infra/ in this phase. For tasks spanning independent areas, launch 2–3 search subagents in parallel../docs/plan.md from resources/plan-template.md and ./.azure/deployment-plan.md from resources/deployment-plan-template.md. For the AZD template, present 4 options: accept the suggestion from resources/azd-templates.md, pick a different template from the catalog, minimal (azd init --minimal), or none (opt out of azd init). Verify the proposed resource group does not exist (az group exists --name <name>) and suggest a suffix on collision. Mark genuine unknowns as [NEEDS CLARIFICATION: <question>] rather than guessing. Show a summary to the user..gitignore entries for the ./.azure/ folder and any other generated files that should not be checked in.Summarize ./docs/plan.md and ./.azure/deployment-plan.md, and prompt the user to continue with implement.
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 implementation exists and needs to be exercised locally against provisioned Azure dependencies, before deploying.
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`.