Skip to content

Agentic System

cimpl-azure-provisioning includes a multi-agent AI system that serves as the developer's primary interface to the project. Three AI contexts — a base copilot and two specialized agents — collaborate through shared skills, a persistent knowledge vault, and automated workflows to handle everything from daily briefings to dependency remediation.

Architecture

The system follows a simple hierarchy:

  • Base Copilot handles infrastructure-as-code work directly (Terraform, Helm, AKS, azd)
  • Wingman manages productivity, strategy, and cross-cutting concerns — it can delegate to OSDU
  • OSDU Agent specializes in platform operations across 30+ OSDU services

Agents share a library of 13+ skills (reusable capabilities triggered by context), a persistent Obsidian vault for knowledge, and MCP-based semantic search for retrieval.

Agent Architecture

Design Philosophy

Principle Implementation
Agents specialize Each agent has a clear domain boundary and doesn't overlap
Skills compose Shared skills are available to any context; agent-specific skills extend capabilities
Vault persists Decisions, reports, and goals survive across conversations
Routing dispatches Signal-based routing table sends tasks to the right agent automatically

  • Agents

    Wingman and OSDU agent profiles, delegation model, and operating modes.

  • Skills & Commands

    Full catalog of 13+ skills, 11 slash commands, and 5 reusable prompts.

  • Knowledge Vault

    Obsidian-based persistent memory with MCP semantic search.

  • Developer Workflows

    Daily briefings, ship-it, clone-and-scan, debug-and-verify, and how to extend.

Getting Started

Prerequisites:

  • Claude Code CLI installed and configured
  • Repository cloned with worktree layout (see CONTRIBUTING.md)
  • MCP server for vault search (configured in .copilot/mcp-config.json)

First commands to try:

# Morning briefing — gathers GitLab activity + vault goals
/gm

# Ship local changes with review + quality checks
/send

# Clone an OSDU repo and scan dependencies
/clone
/dep-scan

Looking for infrastructure details?

The Design section covers the deployment model, infrastructure, platform services, and security architecture that this agentic system operates on.