azure-provisioner

Coordinate multi-phase Azure infrastructure provisioning with Bicep and gatekeeper review.

9|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/TykoDev/SupremeTeam --skill azure-provisioner
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: azure-provisioner
Source: https://github.com/TykoDev/SupremeTeam/tree/main/skills/azure/azure-provisioner
Command: npx skills add https://github.com/TykoDev/SupremeTeam --skill azure-provisioner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Coordinate and manage complex, multi-phase Azure provisioning workflows so teams and assistants do not produce fragmented, unvalidated, or non-recoverable cloud deployments. It removes the manual burden of sequencing planning, IaC design, configuration, execution, verification, gatekeeper review, and persistent run-state management across interruptions.

Core Features & Use Cases

  • Phase orchestration: Delegates sequentially to azure-planner, azure-architect, azure-configurator, azure-deployer, and azure-verifier while owning phase boundaries.
  • Gatekeeper management: Submits each specialist deliverable to gatekeeper-azure, handles APPROVE/REVISE/ESCALATE cycles, and enforces a 3-attempt revision limit with deadlock escalation.
  • Persistence & resume: Initializes and maintains run-state saves, advisory locks, audit trails, and run manifests to support resume, conflict detection, and traceability.
  • Rewind-and-replay on adversarial findings: Implements Phase 5 final adversarial sweep behavior that rewinds to the earliest impacted phase and replays downstream stages before consolidation.
  • Partial and standalone modes: Runs as an admiral-delegated full pipeline or as a standalone user-invoked orchestrator that can accept upstream artifacts and skip phases.
  • Use Case: Automate provisioning of a production landing zone where architecture is designed as Bicep, configuration hardening is required, deployments must be audited, and final verification is adversarially gated.

Quick Start

Ask azure-provisioner to provision and deploy this project to Azure by specifying the target subscription, region, and any deployment constraints.

Frequently Asked Questions about azure-provisioner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate multi-phase Azure infrastructure provisioning with Bicep?▼

Multi-phase Azure infrastructure provisioning is orchestrated by sequentially delegating planning, Bicep architecture, configuration, execution, and verification tasks to specialized phases while managing boundaries and persistent run-state.

Can I resume an interrupted Azure deployment pipeline without losing the run state?▼

Yes, interrupted Azure deployment pipelines can resume without losing run state by initializing and maintaining persistent run-state saves, advisory locks, audit trails, and run manifests to support conflict detection and traceability.

How does gatekeeper review work for Azure infrastructure-as-code deployments?▼

Gatekeeper review for Azure infrastructure-as-code deployments works by submitting specialist deliverables to approval cycles that handle APPROVE, REVISE, or ESCALATE decisions, enforcing a strict three-attempt revision limit with deadlock escalation.

What happens when an adversarial verification sweep finds issues in an Azure deployment?▼

When an adversarial verification sweep finds issues in an Azure deployment, the orchestration rewinds to the earliest impacted phase and replays all downstream stages before final package consolidation.

Can I run Azure provisioning standalone if I already have upstream architecture artifacts?▼

Yes, you can run Azure provisioning standalone if you have upstream artifacts, because the standalone orchestrator mode accepts existing artifacts and skips unnecessary phases instead of requiring the full admiral-delegated pipeline.

What are the limitations of automating Azure landing zone provisioning with phase-based delegation?▼

Limitations of automating Azure landing zone provisioning with phase-based delegation include a strict three-attempt revision limit per gatekeeper cycle before deadlock escalation triggers, and dependency on sequential phase completion for downstream execution.