design-archive

To archive outdated design docs safely, you can update document frontmatter with status metadata and adjust cross-reference points. This process inserts archival notices and validates cross-reference integrity to ensure active documentation links remain unbroken.

Marking a design document as deprecated or obsolete requires updating its frontmatter with a specific archival reason. The archival process handles superseded, deprecated, obsolete, and completed scenarios by applying replacement metadata and adjusting CLAUDE.md pointers.

Yes, you can optionally move archived design documentation to a designated archive directory. The archival process validates cross-reference integrity after the move, ensuring that pointers in CLAUDE.md and other active modules correctly reflect the new file locations.

You need to apply frontmatter updates when design docs transition to an archived status across multiple project modules. This lifecycle management step is required when documents become superseded, deprecated, obsolete, or completed, ensuring metadata accurately reflects their current state.

Yes, archiving design docs explicitly handles CLAUDE.md pointers and cross-reference updates. The process enforces reference integrity by adjusting links within active project modules and validating that no active documentation points incorrectly to the newly archived files.