AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE
PREREQUISITE: The azure-validate skill MUST be invoked and completed with status Validated BEFORE executing this skill.
⛔ STOP — PREREQUISITE CHECK REQUIRED
Before proceeding, verify BOTH prerequisites are met:
- azure-prepare was invoked and completed →
.azure/deployment-plan.md exists
- azure-validate was invoked and passed → plan status =
Validated
If EITHER is missing, STOP IMMEDIATELY:
- No plan? → Invoke azure-prepare skill first
- Status not
Validated? → Invoke azure-validate skill first
⛔ DO NOT MANUALLY UPDATE THE PLAN STATUS
You are FORBIDDEN from changing the plan status to Validated yourself. Only the azure-validate skill is authorized to set this status after running actual validation checks. If you update the status without running validation, deployments will fail.
DO NOT ASSUME the app is ready. DO NOT SKIP validation to save time. Skipping steps causes deployment failures. The complete workflow ensures success:
azure-prepare → azure-validate → azure-deploy
Scope: This skill executes deployments. It does not create applications, generate infrastructure code, or scaffold projects. For those tasks, use azure-prepare.
APIM / AI Gateway: Use this skill to deploy applications whose APIM/AI gateway infrastructure was already created during
azure-prepare. For creating or changing APIM resources, see
APIM deployment guide. For AI governance policies, invoke
azure-aigateway skill.
⛔ URL FORMAT RULE
When presenting endpoint URLs to the user, you
MUST always use fully-qualified URLs with the
https:// scheme (e.g.
https://myapp.azurewebsites.net, not
myapp.azurewebsites.net). Many Azure CLI commands return bare hostnames without a scheme — always prepend
https:// before presenting them.
⛔ VALIDATION PROOF CHECK
When checking the plan, verify the Validation Proof section (Section 7) contains actual validation results with commands run and timestamps. If this section is empty, validation was bypassed — invoke azure-validate skill first.