What problem does it solve? Finalizing a completed OpenSpec change involves checking artifact and task completion, reconciling delta specs with main specs, and moving the change into an archive directory; doing this manually is error-prone and easy to get wrong. ## Core Features & Use Cases - Guided change selection: Infers the change from context, auto-selects when only one active change exists, or prompts with a list of active changes. - Completion and sync checks: Verifies artifact status via openspec status --json, checks tasks.md for incomplete checkboxes, and assesses whether delta specs need syncing into main specs before archiving. - Safe archiving with verification: Runs the inline spec-sync workflow when requested, verifies the merged main specs, then moves the change into a date-prefixed archive folder with a clear summary. - Use Case: After finishing implementation of a user-auth change, ask the agent to archive it; the skill confirms tasks are done, syncs the delta spec into openspec/specs/user-auth/spec.md, and moves the change to changes/archive/2026-09-22-user-auth/. ## Quick Start Ask the agent to archive the completed OpenSpec change named add-user-auth and sync its delta specs first.
