Map each spec clause to evidence and categorize proof types.
npx skills add https://github.com/Will-Aveva/phoenix-chassis --skill auditor
Please help me install this Agent Skill. Skill: auditor Source: https://github.com/Will-Aveva/phoenix-chassis/tree/main/.agent/skills/auditor Command: npx skills add https://github.com/Will-Aveva/phoenix-chassis --skill auditor
Ensures every spec clause is accounted for and evidenced, preventing uncited assertions and aiding regulatory or standards conformance.
Load the official spec and all relevant artifacts, map every clause to supporting evidence, then generate the audit report.
High-intent search queries and answers about installing and using this skill.
To verify spec conformance, you map each spec clause to evidence within your project artifacts. This process categorizes proof types as direct, indirect, or none, ensuring no uncited assertions remain before regulatory release.
A coverage map is a structured audit output that visualizes spec clause verification across artifacts. It highlights integration coverage, identifies gaps, flags false confidence from uncited assertions, and provides actionable recommendations for compliance teams.
You audit a product spec by loading the official spec and all related documents, then mapping every clause to supporting evidence. This flags uncited assertions and categorizes proof types to ensure complete standards conformance.
Yes, conformance mapping applies the audit to the spec, plan, and related documents to generate a coverage map. This identifies integration coverage gaps, false confidence, and uncited assertions to certify alignment before product release.
The best way to categorize proof types is to map each spec clause against provided artifacts and label the evidence as direct, indirect, or none. This structured audit output reveals coverage gaps and false confidence in the documentation.
Your spec audit shows false confidence because conformance mapping flags uncited assertions within the artifacts. By categorizing proof types as direct, indirect, or none, the audit exposes gaps where documentation implies compliance without actual evidence.
mattphanmImplement approved atomic specs and generate implementation evidence.
augustoheissAssess and remediate technical compliance gaps for SOC 2, ISO 27001, HIPAA, and PCI-DSS.
manuelbrandner85Automate continuous fuzz testing to identify security vulnerabilities and stability regressions.
garethdaineAnalyze supplier audit reports, certifications, SLAs, and regulatory data to assign composite risk ratings.
