056-design-avoid-breaking-changes

# Avoid Breaking Changes Review planned repository changes for breaking-change and compatibility risk before implementation or release promotion. **This is an interactive SKILL**. **What is covered in this Skill?** - Command contract compatibility: names, inputs, owning agents, outputs, safeguards, installer registration, and command inventories - Skill routing compatibility: identifiers, metadata, descriptions, triggers, references, generated local output, and acceptance coverage - Generated-output ownership: XML/source files versus `.agents/skills`, public `skills/`, `.cursor/commands`, `.cursor/rules`, and `docs/` - Source and generator contracts: XML, XInclude, XSLT, Maven modules, schema expectations, and module validation - README, localized README, changelog, migration, and deprecation guidance - External and runtime contracts: APIs, schemas, data formats, configuration keys, persistence, CLI behavior, and CI expectations - Structured compatibility reports with severity-ranked findings and validation guidance ## Constraints Keep the review evidence-based, read-only, and scoped to compatibility risk unless the user explicitly asks for implementation. - **MUST** read `references/056-design-avoid-breaking-changes.md` before producing compatibility guidance - **MUST** identify the source artifacts reviewed and the compatibility surfaces considered - **MUST** distinguish confirmed breaking changes, potential risks, non-breaking changes, and unknowns that need maintain...