agentleFS
Sign inStart free
LIDR-academyLIDR-academy/AI4Devs-LTI-extended/.cursor/skills/openspec-archive-change/SKILL.md

openspec-archive-change

Skill278 starsChanged 6 months agoMITView on GitHub

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

We split this skill into the rules it gives an agent

17 rules. 6 are common, 6 are distinctive, and 5 are very specific to this project.

  • 6

    Common

    Most of the 123 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

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

    Run openspec list --json to get available changes.

    line 20
  2. Distinctive:

    IMPORTANT: Do NOT guess or auto-select a change.

    line 25
  3. Very specific:

    Run openspec status --change "<name>" --json to check artifact completion.

    line 29
  4. Distinctive:

    Use AskUserQuestion tool to confirm user wants to proceed

    line 37
  5. Very specific:

    Read the tasks file (typically tasks.md) to check for incomplete tasks.

    line 42
  6. Very specific:

    Check for delta specs at openspec/changes/<name>/specs/.

    line 55
  7. Common:

    If changes needed: "Sync now (recommended)", "Archive without syncing"

    line 63
  8. Common:

    If already synced: "Archive now", "Sync anyway", "Cancel"

    line 64
  9. Distinctive:

    If user chooses sync, use Task tool (subagent_type: "general-purpose", prompt: "Use Skill tool to invoke openspec-sync-specs for change …

    line 66
  10. Distinctive:

    Create the archive directory if it doesn't exist:

    line 70
  11. Common:

    If yes: Fail with error, suggest renaming existing archive or using different date

    line 78
  12. Common:

    If no: Move the change directory to archive

    line 79
  13. Distinctive:

    Always prompt for change selection if not provided

    line 108
  14. Very specific:

    Use artifact graph (openspec status --json) for completion checking

    line 109
  15. Common:

    Don't block archive on warnings - just inform and confirm

    line 110
  16. Distinctive:

    If sync is requested, use openspec-sync-specs approach (agent-driven)

    line 113
  17. Common:

    If delta specs exist, always run the sync assessment and show the combined summary before prompting

    line 114

“Common” is measured: kept by at least 6 in 10 of the 123 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 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

    If no tasks file exists: Proceed without task-related warning.

  4. Assess delta spec sync state

    Check for delta specs at openspec/changes/<name>/specs/. If none exist, proceed without sync prompt.

    If delta specs exist:

    • Compare each delta spec with its corresponding main spec at openspec/specs/<capability>/spec.md
    • Determine what changes would be applied (adds, modifications, removals, renames)
    • Show a combined summary before prompting

    Prompt options:

    • If changes needed: "Sync now (recommended)", "Archive without syncing"
    • If already synced: "Archive now", "Sync anyway", "Cancel"

    If user chooses sync, use Task tool (subagent_type: "general-purpose", prompt: "Use Skill tool to invoke openspec-sync-specs for change '<name>'. Delta spec analysis: <include the analyzed delta spec summary>"). Proceed to archive regardless of choice.

  5. Perform the archive

    Create the archive directory if it doesn't exist:

    mkdir -p openspec/changes/archive

    Generate target name using current date: YYYY-MM-DD-<change-name>

    Check if target already exists:

    • If yes: Fail with error, suggest renaming existing archive or using different date
    • If no: Move the change directory to archive
    mv openspec/changes/<name> openspec/changes/archive/YYYY-MM-DD-<name>

  6. Display summary

    Show archive completion summary including:

    • Change name
    • Schema that was used
    • Archive location
    • Whether specs were synced (if applicable)
    • Note about any warnings (incomplete artifacts/tasks)

Output On Success

## Archive Complete

**Change:** <change-name>
**Schema:** <schema-name>
**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
**Specs:** ✓ Synced to main specs (or "No delta specs" or "Sync skipped")

All artifacts complete. All tasks complete.

Guardrails

  • Always prompt for change selection if not provided
  • Use artifact graph (openspec status --json) for completion checking
  • Don't block archive on warnings - just inform and confirm
  • Preserve .openspec.yaml when moving to archive (it moves with the directory)
  • Show clear summary of what happened
  • If sync is requested, use openspec-sync-specs approach (agent-driven)
  • If delta specs exist, always run the sync assessment and show the combined summary before prompting

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