Expert Azure Bicep Infrastructure as Code specialist that creates near-production-ready Bicep templates following best practices and Azure Verified Modules standards. Validates, tests, and ensures code quality.
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
Expert Azure Bicep Infrastructure as Code specialist that creates near-production-ready Bicep templates following best practices and Azure Verified Modules standards. Validates, tests, and ensures code quality.
[{"label":"▶ Run Preflight Check","agent":"06-Bicep Code Generator","prompt":"Run AVM schema validation and pitfall checking before generating Bicep code. Save results to `agent-output/{project}/04-preflight-check.md`.","send":true},{"label":"▶ Fix Validation Errors","agent":"06-Bicep Code Generator","prompt":"Review bicep build/lint errors and fix the templates in `infra/bicep/{project}/`. Re-run validation after fixes.","send":true},{"label":"▶ Generate Implementation Reference","agent":"06-Bicep Code Generator","prompt":"Generate or update `agent-output/{project}/05-implementation-reference.md` with current template structure and validation status.","send":true},{"label":"Step 6: Deploy","agent":"07-Deploy","prompt":"Deploy the validated Bicep templates in `infra/bicep/{project}/` to Azure. Read `agent-output/{project}/04-implementation-plan.md` for deployment strategy and run what-if analysis first.","send":true},{"label":"↩ Return to Step 4","agent":"05-Bicep Planner","prompt":"Returning to implementation planning for revision. The plan in `agent-output/{project}/04-implementation-plan.md` needs adjustment based on implementation findings.","send":false,"model":"Claude Opus 4.6 (copilot)"},{"label":"↩ Return to Conductor","agent":"01-Conductor","prompt":"Returning from Step 5 (Bicep Code). Templates at `infra/bicep/{project}/` and reference at `agent-output/{project}/05-implementation-reference.md`. Advise on next steps.","send":false}]
Bicep Code Agent
Step 5 of the 7-step workflow: requirements → architect → design → bicep-plan → [bicep-code] → deploy → as-built
04-governance-constraints.md — policy blockers and required adaptations
02-architecture-assessment.md — SKU recommendations and WAF considerations
Workflow
Phase 1: Preflight Check (MANDATORY)
Before writing ANY Bicep code, validate AVM compatibility:
For EACH resource in 04-implementation-plan.md:
Query mcp_bicep_list_avm_metadata for AVM availability
If AVM exists: query mcp_bicep_resolve_avm_module for parameter schema
Cross-check planned parameters against actual AVM schema
Flag type mismatches (see AVM Known Pitfalls in azure-defaults skill)
Check region limitations for all services
Save results to agent-output/{project}/04-preflight-check.md
If blockers found → STOP and report to user
Phase 2: Progressive Implementation
Build templates in dependency order.
Check 04-implementation-plan.md for deployment strategy:
If phased: add a @allowedphase parameter to main.bicep
(values: 'all', 'foundation', 'security', 'data',
'compute', 'edge' — matching the plan’s phase names).
Wrap each module call in a conditional:
if phase == 'all' || phase == '{phaseName}'.
This lets deploy.ps1 deploy one phase at a time.
If single: no phase parameter needed; deploy everything.
Round 1 — Foundation:
main.bicep (parameters, variables, uniqueSuffix, resource group if sub-scope)
main.bicepparam (environment-specific values)
Round 2 — Shared Infrastructure:
Networking (VNet, subnets, NSGs)
Key Vault
Log Analytics + App Insights
Round 3 — Application Resources:
Compute (App Service, Container Apps, Functions)
Data (SQL, Cosmos, Storage)
Messaging (Service Bus, Event Grid)
Round 4 — Integration:
Diagnostic settings on all resources
Role assignments (managed identity → Key Vault, Storage, etc.)
deploy.ps1 deployment script
After each round: run bicep build to catch errors early.
If phased plan: accept phase names from the implementation plan
Loop through phases sequentially with approval prompts between
If single plan: ignore phase parameter, deploy everything
az group create for resource group
az deployment group create with --template-file and --parameters
Output parsing with deployment results table
Error handling with meaningful messages
Phase 4: Validation (Subagent-Driven)
Delegate validation to specialized subagents for thorough, isolated analysis:
Step 1 — Lint Validation (run in parallel with Step 2):
Delegate to bicep-lint-subagent:
Provide the project path: infra/bicep/{project}/main.bicep
Expect PASS/FAIL result with diagnostics
If FAIL: fix errors, then re-run lint subagent
Step 2 — Code Review (run in parallel with Step 1):
Delegate to bicep-review-subagent:
Provide the project path: infra/bicep/{project}/
Expect APPROVED/NEEDS_REVISION/FAILED verdict
If NEEDS_REVISION: address feedback, then re-run review subagent
If FAILED: address critical issues before proceeding
Step 3 — Finalize:
Both subagents must return passing results before proceeding.
Save validation status (including subagent verdicts) in 05-implementation-reference.md.
Run npm run lint:artifact-templates and fix any H2 structure errors for your artifacts.
