overrideslisted

# overrides - the project's own opinions win better-dev ships opinionated defaults, and a project is allowed to disagree with any of them. When someone corrects a default in the middle of the work, that correction is the authority here - not the skill that suggested otherwise. One job: honor the correction now, and offer to make it the standing default, without ever rewriting the shared skill that carried the default. The overrides live in `.better-dev/overrides.md`, a managed block the host agent already ingests. They are read first by every skill and beat anything a default would have done. ## When the user pushes back Someone steers away from what a skill was about to do - a different branch prefix, a spec that lands somewhere else, a phase they want skipped, a house rule the default didn't know about. Pushback also arrives as a wish rather than a complaint - "just handle it yourself", "stop asking me", said at a gate, a hold, or a question moment - and that is a correction to that moment's default, owed the same honor-now / offer-to-stand treatment; when the standing form is an allowance another skill records (auto-merge is `/guardrails-install`'s merge-policy; per-item consent stays the contract's `merge:` line and is never skipped - silence is never consent), route the persist there instead of writing a generic override line. Two things follow, in order: **1. Honor it now.** Apply the correction to the work in front of you immediately. This one is settled the momen