speckit-archive-run

To archive merged feature specs into project memory, validate the feature directory structure first, detect requirement conflicts and gaps, then apply scoped updates to memory artifacts like spec.md, plan.md, and changelog.md to ensure full traceability.

If the .specify/memory/ directory is missing, the archival process bootstraps it automatically by creating the folder and seeding the required spec.md and plan.md files from the feature content or predefined templates.

Detecting requirement ID collisions and dependency conflicts during spec archival involves scanning the merged feature specification against existing memory artifacts to flag duplicate IDs, entity deltas, and missing architecture coverage.

Yes, you can update only the specification file and skip the changelog during spec archival by applying scope modifiers, which selectively target spec.md, plan.md, changelog.md, or agent knowledge files for updates.

Yes, spec archival works with repositories using optional data-model, contracts, research, tasks, and checklists files, validating the required spec.md and plan.md while processing optional files to consolidate the main project memory.

Feature spec archival fails when plan.md is missing because the validation step requires both spec.md and plan.md to exist in the feature directory before applying any scoped updates or conflict detection to the project memory.