wa:develop-review

Acceptance criteria coverage is enforced by verifying every active AC-ID is addressed by at least one committed task. This quality gate checks task completion against your FRD.md and TASKS.md files to ensure full coverage before advancing.

Preventing new TODO comments involves scanning git diffs relative to a base branch to detect any newly introduced TODO or FIXME items. This change hygiene enforcement flags lingering issues as part of the develop review gate.

Gating feature changes requires running the resolved project test suite and linter, then classifying any failures as blocking or advisory based on dev rigor level. The gate produces a DEVELOPMENT-REVIEW artifact recording the final verdict.

Yes, you need TASKS.md and FRD.md files under docs/{feature} to run a develop review. The gate inspects these files to verify task completion, AC-ID coverage, and validate PR phase expectations for feature-branch workflows.

A develop review gate inspects git history and diffs relative to a base branch to confirm every task is committed and detect new TODO/FIXME items. It validates commit coverage and change hygiene before recording the lifecycle verdict.

Yes, quality gate checks can be classified as advisory or blocking. The gate reads the dev rigor level to determine severity, ensuring non-critical lint or test issues can be flagged without fully blocking the transition to the validate phase.