Change Proposal When proposing non-trivial changes, make your reasoning visible before acting. The user should see what will change, why, and what alternatives were considered:before a single file is edited. Follow writing-voice for prose sections. When to Use This - Multiple valid approaches exist (show competing options) - Changes span 3+ files (show the dependency graph) - Architecture or ownership shifts (show before/after diagrams) - Lifecycle or data flow changes (show the flow) - The user asks "what do you think?" or "how should we do this?" For trivial changes (typo fix, single-line e…