feature-completion-audit

To verify feature completion, cross-reference original requirements with implementation evidence to avoid self-assessment biases. This process applies six independent dimensions, including coverage and test evidence, to output a structured audit report with clear gaps.

Auditing a PR for scope deviation involves applying six-dimension evidence-based evaluation to diffs. This identifies missing requirements and scope changes by cross-checking implementation evidence against acceptance alignment and contract integration criteria.

Feature completion audit works for both in-context dialogue-driven audits and PR or diff reviews. It objectively evaluates correctness, edge cases, and test evidence against original requirements regardless of the development context.

Checking test evidence for acceptance alignment requires cross-referencing implementation diffs against original requirements. The audit evaluates test evidence as one of six independent dimensions to determine if acceptance criteria are met.

A feature completion audit evaluates six independent dimensions: coverage, acceptance alignment, correctness and edge cases, contract and integration, test evidence, and scope deviation. Each dimension is assessed to output a structured report with per-item status.

Unhandled edge cases and integration gaps occur when self-assessment biases mask missing requirements. An objective audit enforces correctness, edge case, and contract integration evaluations against original requirements to identify these actionable gaps.