Skip to content

Robertjam954/multimodal_rag_application / .claude/skills/azure-enterprise-infra-planner

azure-enterprise-infra-planner

Verified

Architect and provision enterprise Azure infrastructure from workload descriptions. For cloud architects and platform engineers planning networking, identity, security, compliance, and multi-resource topologies with WAF alignment. Generates Bicep or Terraform directly (no azd). WHEN: 'plan Azure infrastructure', 'architect Azure landing zone', 'design hub-spoke network', 'plan multi-region DR topology', 'set up VNets firewalls and private endpoints', 'subscription-scope Bicep deployment', 'Azure Backup for VM workloads'. PREFER azure-prepare FOR app-centric workflows.

FileKindSize
SKILL.mdskill md3.5 KB
references/bicep-generation.mdmarkdown3.5 KB
references/constraints/README.mdmarkdown1.2 KB
references/constraints/ai-ml.mdmarkdown3.2 KB
references/constraints/compute-apps.mdmarkdown7.8 KB
references/constraints/compute-infra.mdmarkdown4.5 KB
references/constraints/data-analytics.mdmarkdown6.3 KB
references/constraints/data-relational.mdmarkdown4.9 KB
references/constraints/messaging.mdmarkdown2.5 KB
references/constraints/monitoring.mdmarkdown1.7 KB
references/constraints/networking-connectivity.mdmarkdown6.1 KB
references/constraints/networking-core.mdmarkdown7.0 KB
references/constraints/networking-traffic.mdmarkdown4.6 KB
references/constraints/security.mdmarkdown2.4 KB
references/deployment.mdmarkdown3.7 KB
references/pairing-checks.mdmarkdown3.7 KB
references/phases/1-extract-insights.mdmarkdown1.8 KB
references/phases/2-research-best-practices.mdmarkdown2.8 KB
references/phases/3-research-resources.mdmarkdown3.3 KB
references/phases/4-generate-plan.mdmarkdown792 B
references/phases/5-verify.mdmarkdown814 B
references/phases/6-generate-iac.mdmarkdown675 B
references/phases/7-deploy.mdmarkdown1.3 KB
references/resources/README.mdmarkdown1.6 KB
references/resources/ai-ml.mdmarkdown2.1 KB
references/resources/compute-apps.mdmarkdown4.0 KB
references/resources/compute-infra.mdmarkdown2.8 KB
references/resources/data-analytics.mdmarkdown3.0 KB
references/resources/data-relational.mdmarkdown2.6 KB
references/resources/messaging.mdmarkdown2.0 KB
references/resources/monitoring.mdmarkdown1.5 KB
references/resources/networking-connectivity.mdmarkdown3.6 KB
references/resources/networking-core.mdmarkdown4.3 KB
references/resources/networking-traffic.mdmarkdown2.6 KB
references/resources/security.mdmarkdown1.5 KB
references/schema.mdmarkdown2.7 KB
references/terraform-generation.mdmarkdown2.7 KB
references/verification.mdmarkdown2.6 KB
references/waf-checklist.mdmarkdown1.9 KB
references/workflow.mdmarkdown2.6 KB

references/phases/3-research-resources.md

View on GitHub
# Phase 3: Research Resources

> The goal of this phase is to research Azure resources before generating the plan.

## Step 1 - Resource Refinement

### Cross reference WAF

Read [WAF cross-cutting checklist](../waf-checklist.md). For every checklist item, either:
- Add missing resources / harden properties, or;
- Document the intentional omission in `overallReasoning.tradeoffs` and `inputs.subGoals`.

## Insights Integration

Read `.azure/insights.json` produced by Phase 1 and evaluate each insight against the current workload and sub-goals identified in Phase 2:
* If an insight applies, prefer it over defaults — especially for region, SKU tier, security posture, naming, and tagging.
* If an insight doesn't apply, document the intentional omission in `overallReasoning.tradeoffs`.
* Insights can shape both resource selection and property configuration.
* Track each insight you apply in `inputs.insightsApplied` so the user can trace why a decision was made.

> Mandatory Security rule: only apply a security-related insight if it results in an equal or stronger security posture than the alternatives. A weaker security posture from an insight is only acceptable when the user has explicitly requested it in the initial prompt.

## Step 2 - Resource Lookup

> Mandatory: Complete this step for every resource before generating the plan. WAF tools from Phase 2 provide architecture guidance, but do not provide ARM types, naming rules, or pairing constraints. This step fills those gaps.

For each resource identified since Phase 1:
1. Read the relevant resource reference file to get its ARM type, API version, and CAF prefix. Use [resources/README.md](../resources/README.md) as the index to help you find the right file (e.g., `resources/compute-infra.md` for AKS, `resources/data-analytics.md` for Cosmos DB).
2. Read the relevant pairing constraint file using [constraints/README.md](../constraints/README.md) as the index. Each category file is <2K tokens, you must read the whole file for all resources in that category.
3. **Required** — for every resource, spawn a general-purpose sub-agent to fetch its naming rules. Pass the naming rules URL from the resource file and instruct the sub-agent to call `microsoft_docs_fetch` and return only the min/max length, allowed characters, and uniqueness scope. The resource file's CAF prefix is a style convention only — it does not capture these ARM-enforced constraints, so this step cannot be skipped.

> Important Tip: Only load the category files you need. For a plan with AKS + Cosmos DB + VNet + Key Vault, you'd load 4 constraint files and 4 resource files (~5.5K tokens total) instead of the full catalog (~22K tokens).

After completing the steps above, verify from the tool results:

1. Type — Correct `Microsoft.*` resource type and API version
2. SKU — Available in target region, appropriate for workload
3. Region — Service available, data residency met
4. Name — CAF-compliant naming constraints
5. Dependencies — All prerequisites identified and ordered
6. Properties — Required properties per resource schema
7. Alternatives — At least one alternative with tradeoff documented

## Gate
- Every resource has an ARM type, naming rules, and pairing constraints checked.
- Present the preliminary resource list to the user with brief justifications and wait for approval before proceeding.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall