- Run
git status --short --branch. - Run
entire resume <branch>when resuming an existing branch. - Review recent commits touching the affected area.
- Read
task_plan.mdandnotes.md. - For changes touching three or more files, use focused parallel exploration where useful.
- Keep implementation slices bounded by ownership area.
- Avoid logging, writing, or requesting real secret values.
- Update
notes.mdwith findings that affect decisions. - Update
task_plan.mdafter each phase. - Surface security assumptions and compatibility tradeoffs early.
- Run targeted tests for the touched surface.
- Run formatting or lint checks when practical.
- Record unresolved risks and follow-up work.
- Produce a concise readiness report with files changed and verification status.