final-audit

To audit a feature end-to-end, provide the complete feature scope, parent PRD reference, and modified file list to perform a cross-cutting review. This generates a comprehensive audit report covering security, logic, consistency, and best-practice alignment across the implementation.

A cross-cutting code audit inspects the entire feature implementation across multiple modules to identify systemic patterns and inconsistencies. Unlike standard PR reviews that check individual changes, it validates holistic quality, data handling, and architectural decisions across the complete feature boundary.

To run a comprehensive feature audit, you need a complete feature scope definition, the parent PRD reference, and the list of modified files. Supplying these inputs allows the audit to generate a structured findings report ready for remediation planning.

You should perform a final feature audit after feature completion and merge. Applying the audit at this stage ensures the entire implementation is reviewed for systemic issues, security best practices, and best-practice alignment across all modified files before final delivery.

Yes, a feature audit validates alignment with the parent PRD and scope. It inspects the complete implementation to identify gaps between the original requirements and the final code, producing a structured findings report linked directly to the PRD for remediation planning.