routing-coverage-matrix

Cross-references work types against INTENT_RULES to identify routing gaps and collisions.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/Nerfherder16/BrickLayer --skill routing-coverage-matrix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: routing-coverage-matrix
Source: https://github.com/Nerfherder16/BrickLayer/tree/main/.claude/skills/routing-coverage-matrix
Command: npx skills add https://github.com/Nerfherder16/BrickLayer --skill routing-coverage-matrix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Routing coverage analysis identifies gaps, silent zones, first-match collisions, and orphaned rules in routing configurations so teams can improve routing accuracy and deployment reliability.

Core Features & Use Cases

  • Cross-reference routing rules against work types to surface coverage gaps, silent zones, and misrouting.
  • Generate a matrix that highlights where INTENT_RULES match or fail to map to dispatch targets.
  • Use case: inspectors can audit a Masonry/CLAUDE project to ensure all work types have clear routing targets and adjust rules accordingly.

Quick Start

Run a routing coverage analysis on your project to generate a matrix showing coverage, silent zones, and collisions.

Frequently Asked Questions about routing-coverage-matrix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find routing collisions and silent zones in my project?

A routing coverage matrix maps work types against INTENT_RULES to visually highlight coverage gaps and misrouting. It outputs a structured grid showing exactly where dispatch targets fail to match intended work categories.

What is a routing coverage matrix used for?

A routing coverage matrix maps work types against INTENT_RULES to visually highlight coverage gaps and misrouting. It outputs a structured grid showing exactly where dispatch targets fail to match intended work categories.

How do I audit Masonry or CLAUDE routing rules for misrouting?

To audit Masonry routing configurations, you cross-reference INTENT_RULES against work types using the router source file. This generates a matrix that identifies orphaned rules and silent zones to improve deployment reliability.

Do I need the router source file to analyze routing coverage gaps?

Yes, identifying routing coverage gaps requires access to the router source file and the routing target table. Without these inputs, the system cannot cross-reference INTENT_RULES to detect orphaned rules or first-match conflicts.

Why are some routing rules not matching their dispatch targets?

Routing rules miss dispatch targets due to first-match collisions or silent zones in the configuration. Cross-referencing INTENT_RULES against work types reveals these orphaned rules so you can adjust routing targets accordingly.