review-recent-work

A fresh-eyes code review independently inspects plan artifacts, code changes, and test signals to identify correctness gaps. It evaluates whether the implementation achieves intended outcomes and generates a usefulness score with concrete fix suggestions.

A post-implementation review assesses recently completed work to fix obvious bugs and improve readability. It validates outcomes across plan artifacts and related code changes, providing a thorough evaluation of whether the implementation meets its goals.

Yes, you can assess workflow usefulness by inspecting plan artifacts and test signals post-implementation. The review process identifies rough edges, evaluates if intended outcomes are achieved, and outputs a summary with a quantified usefulness score.

To identify bugs and readability issues, perform a fresh-eyes review of the latest work. This process inspects code changes and test signals to surface correctness gaps, rough edges, and suggests concrete fixes to improve overall clarity.

You should conduct a post-implementation review immediately after your ExecPlan is implemented. This timing allows you to catch obvious bugs, improve readability, and validate outcomes while the context is fresh and fixes are easier to apply.

The review process inspects available test signals to validate implementation outcomes across plan artifacts and code changes. It follows a defined workflow to assess usefulness and identify issues, working with the signals present in your current environment.