Generate professional Azure High-Level Design (HLD) documents in Markdown following enterprise standards. Use when creating architecture documentation, HLD, design documents for Azure Landing Zones, or documenting infrastructure. Analyzes Bicep/Terraform code to extract architecture details. Supports template and customer-specific HLD generation.
Generate professional High-Level Design (HLD) documents for Azure infrastructure following the enterprise standard defined in docs/standards/hld-template-standard.md.
Creates a blank HLD template with all required sections pre-structured for manual completion.
Output: Architecture/Templates/HLD/hld-template.md
Usage: Invoke skill without arguments or with --template
Generates a populated HLD document by analyzing existing Bicep/Terraform infrastructure code.
Output: Architecture/Customer/[customercode]/hld/[project-name]-hld.md
Usage: Provide customer code and project name as arguments
Auto-detect mode based on arguments:
--template flag: Template ModeFor Customer Mode, collect:
For Template Mode:
Always read these standard documents:
docs/standards/hld-template-standard.md - HLD structure and requirementsdocs/standards/naming-convention.md - Azure resource naming standardsdocs/standards/ip-addressing-scheme.md - Network IP allocation strategyThese provide the foundation for generating compliant HLD documents.
If generating a template HLD:
Copy the pre-built template:
templates/hld-template.md as the base[TO BE COMPLETED] markersCreate output directory:
mkdir -p Architecture/Templates/HLD
Write template file:
Architecture/Templates/HLD/hld-template.mdInform user:
If generating a customer-specific HLD:
Discover infrastructure files:
**/*.bicep**/*.tfRead and analyze key files:
Bicep: Look for:
Terraform: Look for:
Extract architecture details:
Use the template structure and populate with extracted data:
Document Properties:
Introduction:
Architecture Overview:
Management Groups and Subscriptions:
Network Design:
Identity and Access:
Security and Governance:
Monitoring and Operations:
Azure Region:
Naming Convention:
References:
Create output directory:
mkdir -p Architecture/Customer/[customercode]/hld
Write HLD file:
[project-name]-hld.mdArchitecture/Customer/[customercode]/hld/[project-name]-hld.mdAdd review notes:
[REVIEW REQUIRED]Before finalizing, verify:
After generating the HLD:
Confirm completion:
Next steps guidance:
Related documentation:
/hld-generator
/hld-generator --template
/hld-generator --customer <customercode> --project <project-name>
/hld-generator --customer contoso --project azure-landing-zone
/hld-generator --customer fabrikam --project hub-spoke-network --path infrastructure/bicep
Arguments:
--customer <code>: Customer identifier (e.g., contoso, fabrikam)--project <name>: Project name for the HLD filename--path <path>: Optional specific path to infrastructure code to analyze--template: Explicitly request template mode (default if no customer specified)User request: "Create a blank HLD template"
Skill action:
User request: "/hld-generator --customer contoso --project azure-landing-zone"
Skill action:
bicep/management-groups.bicepbicep/networking/hub.bicep and bicep/networking/spoke.bicepbicep/policies/User request: "/hld-generator --customer fabrikam --project network-infrastructure --path infrastructure/terraform/networking"
Skill action:
infrastructure/terraform/networking/ directorymain.tf: Hub VNet configurationvariables.tf: IP ranges and naming variablesspoke.tf: Spoke VNet modulesIssue: No infrastructure code found Solution:
Issue: Generated HLD is too detailed Solution:
Issue: Cannot determine network topology Solution:
Issue: IP ranges don't match ip-addressing-scheme.md Solution:
Standards Documents (must exist):
docs/standards/hld-template-standard.mddocs/standards/naming-convention.mddocs/standards/ip-addressing-scheme.mdOutput Directories:
Architecture/Templates/HLD/Architecture/Customer/[customercode]/hld/Supported Code Formats: