Openspec Archive Change
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
Install
npx skills add rpamis/comet --skill openspec-archive-changegit clone --depth 1 https://github.com/rpamis/comet.git /tmp/comet
mkdir -p ~/.claude/skills
cp -r /tmp/comet/eval/local/skills/benchmarks/dependency/openspec/openspec-archive-change ~/.claude/skills/openspec-archive-changePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
Archive a completed change in the experimental workflow. **Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes. **Steps** 1. **If no change name provided, prompt for selection** Run `openspec list --json` to get available changes. Use the **AskUserQuestion tool** to let the user select. Show only active changes (not already archived). Include the schema used for each change if available. **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose. 2. **Check artifact completion status** Run `openspec status --change "<name>" --json` to check artifact completion. Parse the JSON to understand: - `schemaName`: The workflow being used - `artifacts`: List of artifacts with their status (`done` or other) **If any artifacts are not `done`:** - Display warning listing incomplete artifacts - Use **AskUserQuestion tool** to confirm user wants to proceed - Proceed if user confirms 3. **Check task completion status** Read the tasks file (typically `tasks.md`) to check for incomplete tasks. Count tasks marked with `- [ ]` (incomplete) vs `- [x]` (complete). **If incomplete tasks found:** - Display warning showing count of incomplete tasks - Use **AskUserQuestion tool** to confirm user wants to proceed - Proceed if user confirms
Details
- Skill name
openspec-archive-change- Repository
- rpamis/comet
- Path
eval/local/skills/benchmarks/dependency/openspec/openspec-archive-change/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
FAQ
What does the Openspec Archive Change skill do?
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
How do I install the Openspec Archive Change skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add rpamis/comet --skill openspec-archive-change. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Openspec Archive Change popular?
It lives in rpamis/comet, which has 3,306 GitHub stars and 317 forks.
Related skills
Brainstorming
3.3krpamis/comet
Transforms rough ideas into fully-formed designs. Structure your brainstorming sessions and develop ideas systematically.
Dispatching Parallel Agents
3.3krpamis/comet
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Finishing a Development Branch
3.3krpamis/comet
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Openspec Continue Change
3.3krpamis/comet
Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.
Openspec Apply Change
3.3krpamis/comet
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
Openspec New Change
3.3krpamis/comet
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.