agentleFS
Sign inStart free
redhat-developerredhat-developer/rhdh-skills/skills/refinement/openspec-archive-change/SKILL.md

openspec-archive-change

Skill20 starsChanged 20 days agoApache-2.0View on GitHub

Archives a completed OpenSpec change into openspec/changes/archive/, after confirming artifact and task completion and offering to sync any delta specs into the main specs first. Use for "archive this change", "finalize <change>", or "this is done, wrap it up". Warns but does not block on incomplete artifacts or tasks — the user decides whether to proceed anyway.

146 other projects use a version of this, 63 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use source-command-opsx-apply, source-command-opsx-archive and 4 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • antech2-asyncSkill

    source-command-opsx-apply

    Implement tasks from an OpenSpec change (Experimental)

    Also in 5 projects that use this

  • antech2-asyncSkill

    source-command-opsx-archive

    Archive a completed change in the experimental workflow

    Also in 5 projects that use this

  • Microsoft AzureSkill

    openspec-update-change

    Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.

    Also in 91 projects that use this

  • goernSkill

    draft-openspec-docs

    Collaborative page-drafting mode for the OpenSpec docs. Builds a scratch plan inside the target page (purpose, structure, numbered draft steps), iterates on it with the user, then drafts one section per approved step and cleans up after itself. Use when a page needs a from-scratch rewrite or a new page is being shaped with the user in the loop.

    Also in 3 projects that use this

  • +2 more from antech2-async

The file

We split this skill into the rules it gives an agent

6 rules. 2 are common, 0 are distinctive, and 4 are very specific to this project.

  • 2

    Common

    Most of the 142 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Select the change: If not given, run openspec list --json, show only active (non-archived) changes with their schema, and let the user …

    line 19
  2. Very specific:

    Check task completion: Read the tasks file (typically tasks.md), count - [ ] vs - [x].

    line 25
  3. Very specific:

    Assess delta spec sync state: Check openspec/changes/<name>/specs/.

    line 28
  4. Very specific:

    Use the current date. If the target directory already exists, fail with an error and suggest renaming the existing archive or using a …

    line 44
  5. Common:

    Always prompt for change selection if not given — never auto-select.

    line 63
  6. Common:

    If delta specs exist, always run the sync assessment and show the combined summary before prompting, regardless of the user's eventual …

    line 66

“Common” is measured: kept by at least 6 in 10 of the 142 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Archive an OpenSpec change

Move a change from active to archived, confirming completeness and offering to sync its delta specs into the long-lived main specs first.

Steps

  1. Select the change. If not given, run openspec list --json, show only active (non-archived) changes with their schema, and let the user choose. Never guess.
  2. Check artifact completion: openspec status --change "<name>" --json — read schemaName and each artifact's status. If any are not done, show a warning listing them and confirm the user wants to proceed anyway.
  3. Check task completion. Read the tasks file (typically tasks.md), count - [ ] vs - [x]. If incomplete tasks exist, warn with the count and confirm before proceeding. No tasks file means no warning needed.
  4. Assess delta spec sync state. Check openspec/changes/<name>/specs/. If delta specs exist, compare each against its main spec at openspec/specs/<capability>/spec.md, determine what would change, and show a combined summary before offering: "Sync now (recommended)" vs "Archive without syncing" (or, if already synced, "Archive now" / "Sync anyway" / "Cancel"). If the user chooses sync, delegate via the Task tool (subagent_type: general-purpose) with the prompt "Invoke /openspec-sync-specs for change '<name>'" plus the analyzed delta summary — then archive regardless of the sync choice made.

  5. Perform the archive:

    mkdir -p openspec/changes/archive
mv openspec/changes/<name> openspec/changes/archive/YYYY-MM-DD-<name>

    Use the current date. If the target directory already exists, fail with an error and suggest renaming the existing archive or using a different date. .openspec.yaml moves with the directory automatically.

  6. Display a summary: change name, schema, archive location, whether specs were synced, and any warnings from steps 2-3.

Output

## Archive Complete

**Change:** <change-name>
**Schema:** <schema-name>
**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
**Specs:** synced to main specs / no delta specs / sync skipped

Guardrails

  • Always prompt for change selection if not given — never auto-select.
  • Warnings inform and require confirmation; they never silently block.
  • Preserve .openspec.yaml when moving to archive.
  • If delta specs exist, always run the sync assessment and show the combined summary before prompting, regardless of the user's eventual choice.

Completion

Complete when the change directory has moved to openspec/changes/archive/YYYY-MM-DD-<name>/, any chosen spec sync has run, and the summary — including every warning surfaced along the way — has been shown to the user.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free