write-maintainable-code

# Write Maintainable Code Use the fewest concepts that satisfy the already-approved result and its acceptance evidence. Minimize current maintenance burden, not raw line count. ## Keep the ownership boundary This skill is a subordinate implementation lens inside the public method: - During CONVERGE, generate code/no-code route alternatives and possible code ownership seams. Let `reasoning-doctrine` own the stage, recommendation, rejected alternatives, hard stops, safe outcome slice, and transition to execution. - During EXECUTE, apply this lens to the selected route. Do not redefine the selected outcome, acceptance evidence, safe slice, or mutation method. - During an authorized repair, apply only this execution lens. `run-review-repair-loop` continues to own review, scoring, and repair iteration. - When governance is active, let `governed-operator` own authority, seats, scope, the formal contract, verdicts, publication boundaries, and Done. If the outcome or acceptance evidence is unresolved, return to `reasoning-doctrine`. If authority, seat responsibility, scope, or publication authority is unresolved, return to `governed-operator`. If a finished change needs review-only grading, use `run-review-repair-loop` and keep its Builder self-review separate from the independent-review and Done boundaries owned by `governed-operator`; do not score or approve under this lens. Re-enter this skill only for an authorized repair. ## Compare routes before adding code ...