completeness-auditor

To verify audit artifacts for completed skills, you need to check that each completion claim is backed by an on-disk artifact containing at least five explicit pass items. This process enforces presence, content standards, and recency against source changes.

Workflow validation blocks progression when audit artifacts are missing, empty, or contain fewer than five explicit pass items. This ensures verifiability and prevents verbal claims from constituting completion within the independent audit layer.

You can audit completeness across the pipeline by running a tool that verifies every completion claim against substantive on-disk artifacts. This process outputs a structured completeness_audit.md report detailing any missing or insufficient items.

A completeness audit requires at least five explicit pass items to ensure that every completion claim is substantive and verifiable. This standard prevents verbal claims from constituting completion within the independent audit layer.

Yes, this completeness validation runs in parallel with the consistency-auditor and precedes the quality-assurance-auditor. This sequence enforces a robust audit chain across the entire QA workflow.

To enforce traceable repair paths, you should validate the presence and content of required audit artifacts across the QA workflow. Blocking progression when artifacts are missing or insufficient ensures all completion claims are traceable and backed on disk.