speckit-review

To validate code against specifications and update task status, perform a structured code review of completed implementation work, verifying it meets acceptance criteria and automatically marking completed tasks in tasks.md.

Automating task status updates after a code review involves validating implementation work against spec.md requirements, and if approved, automatically marking the associated tasks as complete in the tasks.md file.

Code review validation for speckit project structures works by loading context from feature paths, specifications, and task lists within the .specify/ directory to satisfy requirements for code quality, test validation, and acceptance criteria verification.

Yes, you need a .specify/ directory to validate code against acceptance criteria, as this structured code review process applies specifically to speckit project structures and requires loading context from feature paths and specifications.

You can verify test validation and code quality without manually checking spec.md by running a structured review process that loads specification context automatically and validates completed implementation work against the defined acceptance criteria.

You should not use automated task status updates in tasks.md when the implementation work has not been fully completed, as the review process requires validating finished code against specifications before marking tasks as complete.