What problem does it solve?
This Skill provides a disciplined process for removing parsed-but-unenforced properties from the ObjectStack specification without leaving silent no-ops, stale documentation, broken migrations, or inconsistent generated artifacts.
Core Features & Use Cases
- Removal Route Selection: Determines whether a property requires a retired-key tombstone, strict schema removal, or no action because nothing parses it.
- Repository-Wide Change Management: Coordinates liveness ledgers, schema definitions, conversions, migration chains, generated baselines, forms, translations, examples, documentation, tests, and changesets.
- Validation and Safety Gates: Uses TypeScript errors, liveness checks, fixture disjointness, migration replay, authorable-surface checks, and package-specific verification commands to catch incomplete retirements.
- Use Case: Apply the Skill when the liveness ledger marks a metadata property as dead and you need to remove it across the specification, migration path, published guidance, and authoring surfaces.
Quick Start
Use this Skill to retire the specified inert metadata property and verify every affected schema, ledger, migration, generated artifact, form, documentation, example, and test gate.