// 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.
| name | spec2cloud |
| description | 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. |
Run the four stages in order using the user's prompt as the spec input. Optimize for autonomy: make the most reasonable choice instead of asking, and record every assumption.
The user's prompt is the spec brief. If empty, ask once for it; otherwise do not ask further clarifying questions.
specify with the user's prompt. Resolve unknowns by best judgment and mark each as [NEEDS CLARIFICATION: <question> — assumed: <value>] in ./docs/spec.md.plan. For each AZD-template choice and Azure region/SKU, pick the minimal viable option and record the assumption in ./docs/plan.md and .azure/deployment-plan.md.implement. On scaffold conflicts, prefer merge over overwrite without asking.deploy and run azd up.[NEEDS CLARIFICATION] blocks correctness (e.g., compliance, data residency, cost ceiling) and no safe default exists.Summarize each stage's output doc, list every assumption made, and hand back the deployed Azure endpoint.
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 starting or refining a project's requirements, before any planning or coding. Supports sub-commands `sync`, `reverse`, and `validate`.