spec-property-retirement

Retire parsed-but-unenforced ObjectStack specification properties across schemas, migrations, and artifacts.

22|6|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/objectstack-ai/objectstack --skill spec-property-retirement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-property-retirement
Source: https://github.com/objectstack-ai/objectstack/tree/main/.claude/skills/spec-property-retirement
Command: npx skills add https://github.com/objectstack-ai/objectstack --skill spec-property-retirement

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about spec-property-retirement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely remove parsed but unenforced metadata properties from a specification?

Safely removing inert metadata properties requires updating liveness ledgers, schemas, ADR-0087 conversions, migration chains, generated baselines, tests, and validation gates to prevent broken migrations and stale documentation.

What is a liveness ledger dead verdict in schema evolution?

A liveness ledger dead verdict identifies parsed but unenforced specification properties as inert, triggering a coordinated retirement across schemas, migration conversions, generated baselines, forms, and validation gates.

When do I need a retired-key tombstone versus strict schema removal?

A retired-key tombstone is needed when a parsed property requires a recorded removal marker, whereas strict schema removal applies when completely deleting the property definition without leaving a parsed trace in the specification.

How do I validate TypeScript errors after retiring schema properties?

Validate TypeScript errors after schema property retirement by running liveness checks, fixture disjointness tests, migration replay, authorable-surface checks, and package-specific verification commands to catch incomplete removals.

What are the limitations of removing inert metadata keys without breaking gates?

Limitations of removing inert metadata keys include leaving silent no-ops, inconsistent authoring surfaces, or uncoordinated updates across migration chains, generated baselines, forms, documentation, and repository checks.