adv-audit

Detect engineering drift by comparing codebases against specifications and enforcing quality gates.

4|Updated Jan 22, 2026

Search Tags:#audit #drift #specs #quality-gates #conformance #adv

Ready to run

npx skills add https://github.com/Sharper-Flow/Advance --skill adv-audit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: adv-audit
Source: https://github.com/Sharper-Flow/Advance/tree/main/skills/adv-audit
Command: npx skills add https://github.com/Sharper-Flow/Advance --skill adv-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the problem of engineering drift, where the implementation of a project diverges from its original specifications, leading to hidden bugs, orphaned code, and technical debt.

Core Features & Use Cases

Drift Detection: Automatically compares codebase implementation against defined specs to identify missing requirements or constraint violations.
Quality Gate Enforcement: Validates project health against strict thresholds for drift, ambiguity, and test coverage.
Use Case: Run an audit before a release to ensure that all MUST and SHALL requirements are implemented and that no orphaned code or conflicting specs remain in the repository.

Quick Start

Execute the adv-audit skill to perform a full project conformance check and generate a quality report.

Frequently Asked Questions about adv-audit

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

FAQPage Schema

What is spec-to-code drift detection and how does it find orphaned code?▼

Spec-to-code drift detection identifies discrepancies between engineering specifications and codebase implementation. It scans project worktrees to map requirements, automatically finding orphaned code and normative language violations where implementation diverges from defined specs.

How do I automate conformance checks for MUST and SHALL requirements before a release?▼

To automate conformance checks, execute an automated drift scan across project worktrees. This validates that all MUST and SHALL requirements are implemented and enforces quality gates based on predefined thresholds for coverage, ambiguity, and architectural alignment.

Can I enforce quality gates for test coverage and architectural alignment automatically?▼

Yes, you can enforce quality gates automatically by validating project health against strict predefined thresholds. This process checks for requirement coverage, ambiguity, and architectural alignment to ensure codebase implementation meets defined spec conformance standards.

Does automated requirement mapping work across multiple project worktrees?▼

Automated requirement mapping works across project worktrees to identify missing requirements and constraint violations. It operates across the codebase implementation to detect orphaned code, normative language violations, and conflicting specs.

What is the best way to find conflicting specs and normative language violations in a codebase?▼

The best way to find conflicting specs is through automated drift scanning. This process compares codebase implementation against defined engineering specifications to identify normative language violations and spec conflicts.

When should I run a spec-to-code audit to prevent engineering drift?▼

You should run a spec-to-code audit before a release to prevent engineering drift. This ensures all normative requirements are implemented, validates project health against quality gates, and confirms no orphaned code remains in the repository.