skills.rest
girlguidingstaplehurst
girlguidingstaplehurstOFFICIAL
Explore all skills by this author →
GitHub

openspec-archive-change

Archives completed OpenSpec changes after verifying artifacts, tasks, and spec sync state.

Updated Mar 7, 2024
Search Tags:#workflow#cli#archive#change management#spec-driven development#openspec#delta specs
One-click install
npx skills add https://github.com/girlguidingstaplehurst/booking --skill openspec-archive-change-girlguidingstaplehurst
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/girlguidingstaplehurst/booking/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/girlguidingstaplehurst/booking --skill openspec-archive-change-girlguidingstaplehurst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in an OpenSpec workflow requires checking artifact completion, task status, and delta spec synchronization before moving the change into an archive directory; doing this manually is error-prone and easy to get out of order. ## Core Features & Use Cases - Guided archive workflow: Selects the change (with prompts when ambiguous), checks artifact and task completion via openspec status --json, and confirms before proceeding on warnings. - Delta spec sync verification: Compares delta specs against main specs, optionally runs an inline sync, and re-verifies every capability before archiving. - Store-aware operation: Supports registered OpenSpec stores via --store <id> flags discovered with openspec store list --json. - Use Case: After finishing implementation of a user-auth change, ask the assistant to archive it; the skill validates completion, syncs specs if needed, and moves the change to changes/archive/YYYY-MM-DD-user-auth. ## Quick Start Ask the assistant to archive the completed OpenSpec change named add-booking-form and confirm any warnings it reports.

Frequently Asked Questions about openspec-archive-change

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

FAQPage Schema
How do I archive a completed OpenSpec change?▼

Invoke the archive workflow with an optional change name; the skill checks artifact and task completion, assesses delta spec sync state, then moves the change directory into changes/archive with a YYYY-MM-DD prefix. If the name is ambiguous, it lists active changes and asks you to select one.

What happens if tasks or artifacts are incomplete when archiving?▼

The skill displays a warning listing incomplete artifacts or counting incomplete tasks, then asks for confirmation. It does not block the archive on warnings; it proceeds only after you confirm.

Does archiving sync delta specs to the main specs?▼

Yes, if delta specs exist the skill compares them against main specs and prompts you to sync first or archive without syncing. When you choose sync, it runs the sync inline and re-verifies every capability before moving the change.

Can I archive a change that lives in a registered OpenSpec store?▼

Yes. The skill runs openspec store list --json to discover registered store ids, then appends --store <id> to all commands that read or write specs and changes for the rest of the workflow.

What are the requirements for using this archive workflow?▼

You need the openspec CLI installed and a change managed under an OpenSpec workflow. Without a named store, commands act on the nearest local openspec/ root.

Related Skills

Explore More Software Engineering Skills→
carlosapgomescarlosapgomes

openspec-archive-change

Archive completed OpenSpec changes after validating artifacts and tasks.

Community
Advanced
rangechowrangechow

openspec-sync-specs

Merge delta specs into main specs with idempotent updates.

Community
Advanced
emergent-companyemergent-company
1

openspec-bulk-archive-change

Archive multiple completed changes with openspec CLI after validating status and resolving conflicts.

Official
Advanced
agoodwayagoodway
1

workie

Manage git worktree workflows with branch-isolated PostgreSQL databases for Phoenix/Elixir projects.

Official
Advanced