audit-deck

Finding undocumented defects and doc drift is done by auditing the deck to surface derivation gaps, missing tests, and architectural smells, which are then captured as actionable cards with evidence-backed file and line citations.

The best way to capture architectural smells is auditing the deck to identify inconsistencies and filing new cards via standard workflows with a clear Definition of Done to ensure traceability and reproducibility.

Yes, you can use deck auditing for evidence gathering and phase-aligned triage because it identifies undocumented defects and derivation gaps while applying Definition of Done criteria to ensure reproducibility across project repositories.

To audit a repository for derivation gaps and missing tests, ask the agent to hunt for undocumented defects across the codebase, which then surfaces these inconsistencies as integrated cards for handling in the defect backlog.

Defect hunting relies on a shared defect backlog because it applies to software projects and repositories where integrated card creation files new defects via standard workflows with a clear Definition of Done.

You audit the deck instead of relying solely on standard code review to specifically hunt for undocumented defects, derivation gaps, and doc drift, ensuring reproducibility and traceability through evidence-backed reporting and Definition of Done criteria.