What problem does it solve? Over time, durable project context such as PRODUCT.md, GLOSSARY.md, decision contracts, specs, and agent instructions drifts apart: decisions get duplicated across files, shipped specs pile up, and stale wording conflicts with current meaning. This Skill runs a deliberate hygiene pass that restores consistency across those surfaces without inventing new product intent or overriding unsettled decisions. ## Core Features & Use Cases - Cross-artifact reconciliation: Compares PRODUCT.md, GLOSSARY.md, docs/decisions, docs/specs, and always-loaded instructions (AGENTS.md, CLAUDE.md), removing duplication and obsolete wording while preserving confirmed meaning. - Decision contract normalization: Consolidates duplicate decision files into one contract per subject with required Decisions and Why sections, removes status fields and chronology, and rebuilds the decision index with working links. - Shipped-spec retirement: Preserves reusable decisions from confirmed shipped specs in their owning contracts, then deletes the spec folder; when shipment is ambiguous, it asks instead of guessing. - Use Case: After several releases, your decision folder has three overlapping payments files, AGENTS.md contains a copied decision, and an old spec folder may or may not have shipped. Run this Skill to merge the payments decisions into one current contract, clean AGENTS.md, and get an exact question about the unclear spec instead of a wrong guess. ## Quick Start Use the maintain-project-context skill to reconcile my PRODUCT.md, GLOSSARY.md, docs/decisions, and shipped specs without creating any new decisions.
