agent-coverage-check

Check agent configuration coverage across hierarchy levels and phases. Use to ensure complete agent system coverage.

⭐5stars🔀1forks📁View on GitHub🕐Updated Jan 11, 2026

When & Why to Use This Skill

This Claude skill provides a comprehensive framework for auditing and validating the structural integrity of multi-agent systems. It systematically analyzes agent configurations to ensure 100% coverage across organizational hierarchies (from Chief Architects to Junior Engineers) and development lifecycles (Plan, Test, Implementation, Package, and Cleanup). By identifying missing roles or unassigned phases, it helps developers maintain a robust, gap-free agentic infrastructure.

Use Cases

  • Architectural Gap Analysis: Identify missing agents within specific hierarchy levels (L0-L5) to ensure the system has the necessary oversight and execution capacity.
  • Development Lifecycle Verification: Validate that every phase of the software development process is covered by at least one agent, preventing process breakdowns during implementation or cleanup.
  • System Scaling & Onboarding: Use as a pre-deployment checklist when adding new functional sections like CI/CD or Shared Libraries to ensure orchestrators and specialists are correctly assigned.
  • Configuration Health Checks: Run automated scripts to generate coverage reports that highlight 'Missing Level' or 'Missing Phase' patterns for rapid system debugging.
nameagent-coverage-check
description"Check agent configuration coverage across hierarchy levels and phases. Use to ensure complete agent system coverage."
mcp_fallbacknone
categoryagent

Agent Coverage Check

Verify complete agent system coverage across all dimensions.

When to Use

  • After adding new agents to system
  • Validating agent system completeness
  • Finding gaps in coverage
  • Ensuring all development phases covered

Quick Reference

# Check all coverage dimensions
./scripts/check_agent_coverage.sh

# Check specific dimension
./scripts/check_level_coverage.sh
./scripts/check_phase_coverage.sh
./scripts/check_section_coverage.sh

Coverage Dimensions

Hierarchy Levels:

  • L0: Chief Architect (1)
  • L1: Section Orchestrators (6)
  • L2: Design Agents (per section)
  • L3: Specialists (per module)
  • L4: Engineers
  • L5: Junior Engineers

Development Phases:

  • Plan
  • Test
  • Implementation
  • Package
  • Cleanup

Sections:

  • Foundation
  • Shared Library
  • Tooling
  • First Paper
  • CI/CD
  • Agentic Workflows

Coverage Report Format

Hierarchy Coverage:
  L0: ✅ 1 agent
  L1: ✅ 6 agents
  L2: ✅ 12 agents
  L3: ✅ 24 agents
  L4: ✅ 3 agents
  L5: ✅ 1 agent

Phases:
  Plan: ✅ Covered
  Test: ✅ Covered
  Implementation: ✅ Covered
  Package: ✅ Covered
  Cleanup: ✅ Covered

Sections:
  Foundation: ✅ Orchestrator + agents
  Shared Library: ✅ Orchestrator + agents

Gap Patterns

Missing level: Any level with 0 agents

Missing phase: Phase not assigned to any agent

Missing section: Section without orchestrator

References

  • agent-validate-config - Validate individual agent configs
  • agent-test-delegation - Test delegation completeness
  • .claude/agents/ - All agent configurations