speckit-workflows.review

Automated code review against feature specifications validates completed implementation work by checking Git repository history and `.specify/` configuration. It systematically compares code changes against requirements to ensure adherence before merging.

To update task statuses in `tasks.md`, the review workflow automatically marks completed tasks as done once implementation work passes structural validation. This ensures project progress tracking remains synchronized with approved code quality checks.

Yes, specification validation requires access to Git repository history and `.specify/` project configuration. These dependencies provide the necessary commit context and feature specification data to accurately validate code changes and update task statuses.

The best way to validate code quality and track task completion is using a structured workflow that reviews pending tasks against feature specifications. This approach integrates requirements adherence checks with automated task completion tracking within project files.

Yes, workflow automation can review all pending implementation tasks for a current feature. The process evaluates completed work against specifications, identifies any issues, and prepares validated features for merging by updating task statuses.

Specification validation fails without proper `.specify/` project configuration because the workflow relies on this directory to load feature specifications and implementation plans. Missing configuration prevents the system from accessing the required context for accurate code review.