// Use when starting or refining a project's requirements, before any planning or coding. Supports sub-commands `sync`, `reverse`, and `validate`.
| name | specify |
| description | Use when starting or refining a project's requirements, before any planning or coding. Supports sub-commands `sync`, `reverse`, and `validate`. |
Natural-language description, optionally prefixed with a sub-command:
sync — reconcile spec.md with the current chat history.reverse — generate/update spec.md from existing code in src//infra/.validate — report gaps between current implementation and spec.md.devcontainer — copy resources/devcontainer.json to .devcontainer/devcontainer.json - don't overwrite if it already exists../src/agents/<agent-name> by convention and update ./azure.yaml to include service configuration (host: azure.ai.agent) for each agent../src/mcp/<mcp-server-name> by convention and update ./azure.yaml to include service configuration for each mcp server../src/frontend by convention and update ./azure.yaml to include service configuration for the frontend../src/backend by convention and update ./azure.yaml to include service configuration for the backend. Handle cors configuration between frontend and backend to run locally and when deployed.DefaultAzureCredential; UAMI-bound, keyless RBAC. No connection strings or shared secrets. .env locally; Key Vault / app settings in Azure. User authentication is out of scope unless explicitly required by the user.azd + Bicep with Azure Verified Modules (AVM). Reuse an existing azd template before authoring one. Avoid duplicating resources such as Container Registry, Log Analytics or Application Insights. Private networking is out of scope unless explicitly required by the user..github/skills/specify/resources/copilot-instructions.md to .github/copilot-instructions.md if missing../docs folder if doesn't exist../docs/spec.md from resources/spec-template.md. The spec must be implementation-ready. For genuine unknowns: in interactive mode, ask the user directly; in non-interactive mode, make a best-judgment assumption. All [NEEDS CLARIFICATION] markers must be resolved before the spec is considered implementation-ready.Summarize the changes applied to ./docs/spec.md, and prompt the user to continue with plan (produce a plan only) or implement (plan, then implement in one pass).
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 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.