Small-scope implementation and handoff

Long sessions blur completion state and accumulate unverified assumptions.

Source snapshot imported 2026-10-20. This is not a live feed. Source and contributions.

Workflow guide

Long sessions blur completion state and accumulate unverified assumptions.

Keep scope small, define done before editing, run tests, then compact or hand off before starting another task.

Evidence: public-synthetic-reproduction. Recorded: 2026-09-01.

A change or handoff needs a clear completion record before another task starts.

  1. Write the objective, scope and completion check before editing.
  2. Make the smallest change that satisfies that objective.
  3. Run the relevant checks and retain failures as well as passes.
  4. Hand off the source revision, result, unresolved items and next owner.

Check your result

Another reader can verify the result and continue from the handoff without inferring that a publish or deployment happened.

Limits

  • small slices still require a coordinator to preserve program-level coherence

Session handoff template

Original source