Robertjam954/multimodal_rag_application / .claude/skills/azure-enterprise-infra-planner
azure-enterprise-infra-planner
VerifiedArchitect 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.
references/schema.md
View on GitHub# Infrastructure Plan Schema
```ts
{
meta: {
planId: string // Unique identifier (e.g., "plan-1")
generatedAt: string // ISO 8601 timestamp
version: string // Schema version (e.g., "0.1-draft")
status: "draft" | "approved" | "deployed" // Lifecycle state
}
inputs: {
userGoal: string // User's stated objective or workload description, matches user query exactly
subGoals?: string[] // Inferred architectural constraints and priorities derived from the user's request and research phase. Examples: "Cost-optimized: user chose defaults, avoid premium networking", "Security-first: encrypt all data, use managed identity", "Minimal complexity: single region, no VNet". These help evaluators understand intentional tradeoffs. Should be short list of 0-3 points.
insightsApplied: string[] // For each insight that influenced this plan, cite the insight ID and explain how and why it was applied. Set to an empty array if no insights were applied. Document any unapplied insights in plan.overallReasoning.tradeoffs.
}
plan: {
resources: {
name: string // Logical resource name (CAF-compliant)
type: string // ARM resource type (e.g., "Microsoft.Storage/storageAccounts")
subtype?: string // Exact subtype (e.g., "Blob Storage", "Azure Function")
location: string // Azure region (e.g., "eastus")
sku: string // SKU tier (e.g., "Standard_LRS", "Consumption")
properties?: Record<string, unknown> // Resource-specific properties
reasoning: {
whyChosen: string // Justification referencing WAF pillars (see phases/2-research-best-practices.md and phases/3-research-resources.md) or requirements
alternativesConsidered: string[] // Other options evaluated
tradeoffs: string // Key tradeoffs in this choice
}
dependencies: string[] // Names of resources this depends on (empty if none)
dependencyReasoning?: string // Why these dependencies exist
references: { title: string, url: string }[] // Links to Azure docs
}[]
overallReasoning: {
summary: string // Overall architecture rationale
tradeoffs: string // Top-level tradeoffs and gaps
}
validation: string // Deployment coherence statement
architecturePrinciples: string[] // Guiding principles (e.g., "Highly available", "Secure")
references: { title: string, url: string }[] // Architecture-level doc links
}
}
```
## Insights Schema
```ts
{
id: string // Stable identifier (e.g., "insight-001"); cited from inputs.insightsApplied
pattern: string // Observed fact from the tenant scan (what is true today)
implication: string // Recommended planning action derived from the pattern
}[]
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |