plan-completion-audit

To audit code against a project plan, supply the canonical plan document to the workflow. The audit inventories every planned task, verifies its implementation status across all phases, and reports gaps with file paths and severity levels.

Yes, you can verify your Supabase backend alignment using static analysis. The audit assesses completeness and correctness by mapping planned tasks to implemented code, identifying misalignments and risks before deployment.

The best way to check release readiness is an end-to-end plan-to-build audit. It evaluates the implemented codebase against the canonical project plan to reveal missing work, deviations, and prioritized remediation steps for stakeholders.

Yes, the plan completion audit works with Python and TypeScript codebases. It leverages dependencies such as mypy, pyright, ruff, tsc, and eslint to perform static analysis and assess build alignment across all project phases.

To identify missing features and deviating work, run an audit that compares the canonical project plan against the implemented codebase. It highlights misalignments and delivers actionable remediation guidance with specific file paths.

When running a plan-to-code mapping audit, anticipate limitations regarding dependency detection and static analysis depth. The process requires a canonical project plan and relies on tools like depcheck and npm to inventory tasks accurately.