Compliance Matrix Builder

The problem

Manual compliance mapping is slow, prone to missing "should" vs "shall" distinctions, and often fails to identify specific gaps in draft evidence. Developers and proposal managers struggle to maintain a source of truth between evolving SOW requirements and technical drafts.

What it does

• Extracts every requirement from SOW/PWS files based on specific modals like shall, must, will, should, and may.
• Inventories draft documents to find explicit compliance tags, tables, and heading matches.
• Maps requirements to draft sections with evidence scoring (tagged paragraph, heading only, paraphrase, or none).
• Flags concrete gaps including missing mechanisms, missing boundaries, or missing checks without inventing prose.
• Generates a structured compliance matrix with a header summary, gap register, and unnumbered requirement notes.

Why this beats prompting it yourself

Generic prompts often hallucinate compliance coverage or collapse nuanced modals into a single category. This skill enforces a rigorous three-part test (mechanism, boundary, check) for every requirement and prevents the agent from "fixing" gaps with invented text, ensuring an honest assessment of proposal readiness.

Use cases

• Generating a pink-team compliance matrix from a raw SOW and early-stage draft.
• Performing a book-level coverage check before a final color review to ensure all "should" requirements are met.
• Identifying duplicate claims where multiple sections attempt to own the same SOW requirement.
• Extracting unnumbered requirements from poorly formatted solicitation documents.

Known limitations

Requires structured input files for the SOW and draft. It does not write missing sections or perform page-count reduction, as these are handled by separate specialized skills.