Verified on 2026-08-07.
Plans are first-class repo artifacts.
- small change: lightweight thread-local plan is enough
- non-trivial change: add a checked-in execution plan under
docs/exec-plans/active/ - finished work: move or recreate the plan under
docs/exec-plans/completed/with decisions and verification
Each execution plan should capture:
- problem statement
- scope and non-goals
- decisions made
- progress log
- verification performed
- follow-up debt if any
CI validates Markdown links and important YAML, Compose, and GoReleaser files. The tech debt tracker records recurring checks that still need automation.