om-eject-and-customize

What problem does it solve?

Ejecting and customizing core modules is risky and often avoided. This Skill provides a structured approach to determine when ejecting is necessary, capture the rationale, and execute changes with guardrails to minimize upgrade friction.

Core Features & Use Cases

• Decision framework to evaluate necessity of ejection, document rationale, and consider UMES alternatives.
• Safe ejection workflow including module copy, re-registration, discovery regeneration, and post-ejection validation.
• Upgrade maintenance with a customization log to track changes and guide upstream merges.
• Clear modification boundaries to minimize upgrade risk and avoid destabilizing core behavior.

Quick Start

Initiate an ejection workflow for a core module that UMES extensions cannot solve.