Stale Baseline Guard
Purpose
Avoid acting on outdated context.
When to Use
Use after interruptions, long sessions, branch changes, or concurrent edits.
Inputs
Current files, branch status, latest plan, previous assumptions.
Steps
- Re-read the relevant current state.
- Compare it with the last known state.
- Identify stale assumptions.
- Update the plan before execution.
Gates
Baseline is current or the risk is stated.
Evidence
Fresh file reads, status checks, or updated notes.
Anti-Patterns
Continuing an old plan after files changed.
Related
project-rules-first, claim-verification