147 Workflow Ec10b6fc

Agent and Skill Workflow

Version 8.1.0 | The 7-step infrastructure development workflow

Overview

Agentic InfraOps uses a multi-agent orchestration system where specialized AI agents coordinate through artifact handoffs to transform Azure infrastructure requirements into deployed Bicep code.

The InfraOps Conductor (🎼 Maestro) orchestrates the complete workflow, delegating to specialized agents at each phase while enforcing mandatory approval gates.

Agent Architecture

The Conductor Pattern

%%{init: {'theme':'neutral'}}%%
graph TB
    subgraph "Orchestrator"
        COND["InfraOps Conductor<br/>🎼 Maestro"]
    end

    subgraph "Step 1: Requirements"
        REQ["requirements<br/>📜 Scribe"]
    end

    subgraph "Step 2: Architecture"
        ARCH["architect<br/>🏛️ Oracle"]
        MCP["💰 Azure Pricing MCP"]
    end

    subgraph "Step 3: Design Artifacts"
        DIAG["azure-diagrams<br/>🎨 Skill"]
        ADR["azure-adr<br/>📝 Skill"]
    end

    subgraph "Step 4: Planning"
        PLAN["bicep-plan<br/>📐 Strategist"]
    end

    subgraph "Step 5: Implementation"
        CODE["bicep-code<br/>⚒️ Forge"]
        LINT["lint-subagent"]
        WHATIF["whatif-subagent"]
        REVIEW["review-subagent"]
    end

    subgraph "Step 6: Deployment"
        DEP["deploy<br/>🚀 Envoy"]
    end

    subgraph "Step 7: Documentation"
        DOCS["azure-workload-docs<br/>📚 Skill"]
    end

    COND -->|"delegates"| REQ
    COND -->|"delegates"| ARCH
    COND -->|"invokes"| DIAG
    COND -->|"invokes"| ADR
    COND -->|"delegates"| PLAN
    COND -->|"delegates"| CODE
    CODE -->|"validates"| LINT
    CODE -->|"validates"| WHATIF
    CODE -->|"validates"| REVIEW
    COND -->|"delegates"| DEP
    COND -->|"invokes"| DOCS

    MCP -.->|"pricing data"| ARCH

    style COND fill:#8957E5,color:#fff
    style REQ fill:#e1f5fe
    style ARCH fill:#fff3e0
    style MCP fill:#fff9c4
    style DIAG fill:#f3e5f5
    style ADR fill:#e8eaf6
    style PLAN fill:#e8f5e9
    style CODE fill:#fce4ec
    style DEP fill:#c8e6c9
    style DOCS fill:#e3f2fd

Agent Roster

Primary Orchestrator

Core Agents (7 Steps)

Validation Subagents

Diagnostic Agent

Approval Gates

The Conductor enforces mandatory pause points for human oversight:

Workflow Steps

Step 1: Requirements (📜 Scribe)

Agent: requirements

Gather infrastructure requirements through interactive conversation.

Invoke: Ctrl+Shift+A → requirements
Output: agent-output/{project}/01-requirements.md

Captures:

• Functional requirements (what the system does)
• Non-functional requirements (performance, availability, security)
• Compliance requirements (regulatory, organizational)
• Budget constraints

Handoff: Passes context to architect agent.

Step 2: Architecture (🏛️ Oracle)

Agent: architect

Evaluate requirements against Azure Well-Architected Framework pillars.

Invoke: Ctrl+Shift+A → architect
Output: agent-output/{project}/02-architecture-assessment.md

Features:

• WAF pillar scoring (Reliability, Security, Cost, Operations, Performance)
• SKU recommendations with real-time pricing (via Azure Pricing MCP)
• Architecture decisions with rationale
• Risk identification and mitigation

Handoff: Suggests azure-diagrams skill or bicep-plan agent.

Step 3: Design Artifacts (🎨 Artisan | Optional)

Skills: azure-diagrams, azure-adr

Create visual and textual design documentation.

Trigger: "Create an architecture diagram for {project}"
Output: agent-output/{project}/03-des-diagram.py, 03-des-adr-*.md

Diagram types: Azure architecture, business flows, ERD, timelines

ADR content: Decision, context, alternatives, consequences

Step 4: Planning (📐 Strategist)

Agent: bicep-plan

Create detailed implementation plan with governance discovery.

Invoke: Ctrl+Shift+A → bicep-plan
Output: agent-output/{project}/04-implementation-plan.md, 04-governance-constraints.md

Features:

• Azure Policy compliance discovery
• AVM module selection
• Resource dependency mapping
• Naming convention validation
• Phased implementation approach

Gate 1: User approves the implementation plan before proceeding.

Step 5: Implementation (⚒️ Forge)

Agent: bicep-code

Generate Bicep templates following Azure Verified Modules standards.

Invoke: Ctrl+Shift+A → bicep-code
Output: infra/bicep/{project}/main.bicep, modules/
Output: agent-output/{project}/05-implementation-reference.md

Standards:

• AVM-first approach (Azure Verified Modules from public registry)
• Unique suffix for global resource names
• Required tags on all resources
• Security defaults (TLS 1.2, HTTPS-only, managed identity)

Preflight Validation (via subagents):

Gate 2: User approves preflight validation results.

Step 6: Deployment (🚀 Envoy)

Agent: deploy

Execute Azure deployment with preflight validation.

Invoke: Ctrl+Shift+A → deploy
Output: agent-output/{project}/06-deployment-summary.md

Features:

• Bicep build validation
• What-if analysis before deploy
• Deployment execution with progress tracking
• Post-deployment resource verification

Gate 3: User verifies deployed resources.

Step 7: Documentation (📚 Skills)

Skill: azure-workload-docs

Generate comprehensive workload documentation.

Trigger: "Generate documentation for {project}"
Output: agent-output/{project}/07-*.md

Document Suite:

Agents vs Skills

Quick Reference

Using the Conductor (Recommended)

1. Ctrl+Shift+I → Select "InfraOps Conductor"
2. Describe your infrastructure project
3. Follow guided workflow through all 7 steps with approval gates

Direct Agent Invocation

1. Ctrl+Shift+A → Select specific agent
2. Provide context for that step
3. Agent produces artifacts and suggests next step

Skill Invocation

Automatic: Skills activate based on prompt keywords:

"Create an architecture diagram" → azure-diagrams skill
"Document the decision to use AKS" → azure-adr skill

Explicit: Reference the skill by name:

"Use the azure-workload-docs skill to generate documentation"

Artifact Naming Convention