Skip to content

feedback_keep_docs_in_sync.md

Latest commit

 

History

History
21 lines (18 loc) · 1.11 KB

feedback_keep_docs_in_sync.md

File metadata and controls

21 lines (18 loc) · 1.11 KB
Raw
name feedback-keep-docs-in-sync
description At the END of a task, update ADRs / memory / context docs when (and only when) the work warrants it. Keep decisions recorded; don't over-document trivial changes.
metadata
type
feedback

Rule (2026-05-23): keep ADRs / memory / context in sync at the end of tasks — IF REQUIRED.

Why: the user wants durable decisions captured so we don't reinvent the wheel or relitigate choices, but doesn't want noise (an ADR for every tiny fix).

How to apply:

  • After finishing a unit of work, ask: did this introduce a new library, a new pattern/primitive, an architecture decision, or a hard rule? If yes → write/update an ADR (mtp-docs/adr/) and/or a memory file, and commit it alongside the code.
  • New dependency or architecture-pattern change → ADR is required (per D:\Projects\mtp\CLAUDE.md and the global ADR rules). Bug fixes / minor refactors → no ADR.
  • Recurring preferences, hard rules, and "never do X" guidance → a feedback_* memory + MEMORY.md index line.
  • Do it at the end (not mid-flow), and only when it adds lasting value.