agent-coverage-check

mvillmow's avatarfrom mvillmow

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

⭐8stars🔀4forks📁View on GitHub🕐Updated Jan 3, 2026

When & Why to Use This Skill

The agent-coverage-check skill is a specialized diagnostic tool designed to verify the completeness and structural integrity of multi-agent systems. It systematically audits agent configurations across hierarchical levels, development phases, and functional sections to identify coverage gaps, ensuring that complex agentic workflows are fully staffed and operationally robust.

Use Cases

  • Architectural Audit: Validate that all hierarchy levels, from L0 (Chief Architect) to L5 (Junior Engineers), have the required agent density and assigned roles.
  • SDLC Compliance: Ensure every phase of the software development lifecycle—including Plan, Test, Implementation, Package, and Cleanup—is covered by designated agents.
  • Functional Gap Analysis: Automatically detect missing orchestrators or specialists within specific system sections such as CI/CD, Shared Libraries, or Foundation tooling.
  • System Scaling: Use as a verification gate when expanding agent systems to ensure new modules or layers maintain the required configuration standards.
nameagent-coverage-check
description"Check agent configuration coverage across hierarchy levels and phases. Use to ensure complete agent system coverage."
mcp_fallbacknone
categoryagent
user-invocablefalse

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