agentleFS
PsychQuantPsychQuant/che-ical-mcp/.claude/skills/spectra-archive/SKILL.md

spectra-archive

Skill45 starsChanged 8 months agoMITView on GitHub

Archive a completed change

6 other projects use a version of this, 6 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use spectra-commit, spectra-analyze and 2 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.
  • BananaBay69Skill

    spectra-commit

    Commit files related to a specific Spectra change

    Also in 6 projects that use this

  • harrychuangSkill

    spectra-analyze

    Analyze artifact consistency for a change

    Also in 5 projects that use this

  • harrychuangSkill

    spectra-drift

    Detect drift between a Spectra change and the current codebase state

    Also in 5 projects that use this

  • +1 more from harrychuang

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. 8 are common, 0 are distinctive, and 7 are very specific to this project.

  • 8

    Common

    Most of the 6 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 7

    Very specific

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

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

    Run spectra list --json to get available changes.

    line 23
  2. Common:

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

    line 28
  3. Very specific:

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

    line 32
  4. Very specific:

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

    line 45
  5. Very specific:

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

    line 58
  6. Common:

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

    line 66
  7. Common:

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

    line 67
  8. Common:

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

    line 69
  9. Very specific:

    Use the spectra archive CLI command which handles the full archive workflow (spec snapshot, delta application, @trace injection, identity …

    line 73
  10. Common:

    Always prompt for change selection if not provided

    line 158
  11. Very specific:

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

    line 159
  12. Common:

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

    line 160
  13. Very specific:

    If sync is requested, use the Skill tool to invoke spectra-sync-specs (agent-driven)

    line 163
  14. Common:

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

    line 164
  15. Common:

    If AskUserQuestion tool is not available, ask the same questions as plain text and wait for the user's response

    line 165

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

Input: Optionally specify a change name after /spectra-archive (e.g., /spectra-archive add-auth). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.

Prerequisites: This skill requires the spectra CLI. If any spectra command fails with "command not found" or similar, report the error and STOP.

Steps

  1. If no change name provided, prompt for selection

    Run spectra 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 spectra 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
    • Prompt user for confirmation to continue
    • 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
    • Prompt user for confirmation to continue
    • 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 spectra-sync-specs for change '<name>'. Delta spec analysis: <include the analyzed delta spec summary>"). Proceed to archive regardless of choice.

  5. Perform the archive

    Use the spectra archive CLI command which handles the full archive workflow (spec snapshot, delta application, @trace injection, identity recording, vector indexing):

    spectra archive <name>

    Optional flags:

    • --skip-specs — skip delta spec application (for tooling/doc-only changes)
    • --mark-tasks-complete — mark all incomplete tasks as complete before archiving
    • --no-validate — skip delta spec validation

    If archive fails with "already exists" error, suggest renaming existing archive.

  6. Display summary

    Show archive completion summary including:

    • Change name
    • Schema that was used
    • Archive location
    • Spec sync status (synced / sync skipped / no delta specs)
    • 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

All artifacts complete. All tasks complete.

Output On Success (No Delta Specs)

## Archive Complete

**Change:** <change-name>
**Schema:** <schema-name>
**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
**Specs:** No delta specs

All artifacts complete. All tasks complete.

Output On Success With Warnings

## Archive Complete (with warnings)

**Change:** <change-name>
**Schema:** <schema-name>
**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
**Specs:** Sync skipped (user chose to skip)

**Warnings:**
- Archived with 2 incomplete artifacts
- Archived with 3 incomplete tasks
- Delta spec sync was skipped (user chose to skip)

Review the archive if this was not intentional.

Output On Error (Archive Exists)

## Archive Failed

**Change:** <change-name>
**Target:** openspec/changes/archive/YYYY-MM-DD-<name>/

Target archive directory already exists.

**Options:**
1. Rename the existing archive
2. Delete the existing archive if it's a duplicate
3. Wait until a different date to archive

Guardrails

  • Always prompt for change selection if not provided
  • Use artifact graph (spectra 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 the Skill tool to invoke spectra-sync-specs (agent-driven)
  • If delta specs exist, always run the sync assessment and show the combined summary before prompting
  • If AskUserQuestion tool is not available, ask the same questions as plain text and wait for the user's response

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.