post-task-review

To run a post-task code review, evaluate implementation quality, check edge cases, verify project conventions, and identify potential regressions using a structured review checklist after completing your feature implementation.

A post-task review is a structured validation process that checks completed development tasks for code quality issues, convention violations, documentation gaps, and process improvements to prevent incomplete task delivery.

Analyze documentation impact by evaluating affected documentation using project-specific mappings, identifying stale information, and updating missing details after completing your code refactor or bug fix.

Yes, the task review checklist applies to specification-driven engineering workflows, feature implementations, refactors, and bug fixes, requiring documentation impact analysis and learning extraction procedures for consistent validation.

The best way to extract learnings is to capture reusable discoveries, update project knowledge, and track process improvements as part of a structured post-task evaluation after completing significant code changes.

You should skip post-task reviews for minor or trivial changes, as the process targets significant development work requiring structured validation, convention checking, and documentation impact analysis to be effective.