builder-conventions-k

To prevent codebase drift, implement a deviation protocol that requires stopping to explain plan differences, proposing alternatives with tradeoffs, confirming with the user, and recording decisions before continuing work.

A deviation protocol is a structured process for handling plan changes during execution, needed when milestone-driven development requires strict compliance with coding standards and logged decisions to maintain codebase alignment.

Track progress by marking completed steps with checkboxes in the plan, adding timestamped entries to a progress section, and documenting any surprises or decisions encountered during implementation.

Ensure code matches existing patterns by pausing during development to reflect on established naming conventions and utilities, surfacing observations to the user, and writing simple, robust code without stubs or copy-paste.

Yes, this approach works for codebase maintenance by enforcing codebase reflection prompts that check alignment with established patterns, ensuring new code adheres to existing standards and preventing unlogged architectural drift.

A strict deviation protocol may not suit rapid prototyping or exploratory coding where plan flexibility is essential, as it enforces stopping to explain, propose alternatives, and confirm changes before continuing work.