Summary
When merging PRs to main on private repos, check that ai/product/plans-prds/roadmap.md and ai/product/readme-first.md were updated in the PR branch. Warn if they weren't.
Why
On 2026-03-13, a significant PR was merged to memory-crystal-private (DELETE trigger, cleanup command, doctor fix) without updating the product docs. The roadmap still said v0.7.4 while the code was at v0.7.8. Docs were only updated because Parker explicitly asked. Without that prompt, the next agent would start from stale context.
Proposed solution
A wip-merge command (or wip-release --check-merge) that:
- Diffs the PR branch against main
- Warns if roadmap.md or readme-first.md aren't in the diff
- Asks to proceed or update first
--skip-docs flag to bypass
Complements
The existing product-doc-enforcement plan (release-time check in wip-release). This is the earlier gate: catch it at merge, not at release.
Plan
See ai/product/plans-prds/upcoming/2026-03-13--cc-mini--merge-time-product-doc-check.md
Summary
When merging PRs to main on private repos, check that
ai/product/plans-prds/roadmap.mdandai/product/readme-first.mdwere updated in the PR branch. Warn if they weren't.Why
On 2026-03-13, a significant PR was merged to memory-crystal-private (DELETE trigger, cleanup command, doctor fix) without updating the product docs. The roadmap still said v0.7.4 while the code was at v0.7.8. Docs were only updated because Parker explicitly asked. Without that prompt, the next agent would start from stale context.
Proposed solution
A
wip-mergecommand (orwip-release --check-merge) that:--skip-docsflag to bypassComplements
The existing
product-doc-enforcementplan (release-time check in wip-release). This is the earlier gate: catch it at merge, not at release.Plan
See
ai/product/plans-prds/upcoming/2026-03-13--cc-mini--merge-time-product-doc-check.md