spectra-archive
Skill0 starsChanged 4 months agoMITView on GitHub
Archive a completed change
6 other projects use a version of this, 4 of them edited.
Adopted by
Most recently taken up by
- DanSnow/hoarder-pipetteedited, first seen Oct 8, 2026
- leoho0722/naver-blog-image-downloaderedited, first seen Aug 31, 2026
- PsychQuant/claude-hot-limitword for word, first seen Jul 1, 2026
- harrychuang/cursor-skillsword for word, first seen Jun 17, 2026
- BananaBay69/claude-code-watchdogedited, first seen Apr 29, 2026
- PsychQuant/che-ical-mcpedited, first seen Mar 31, 2026
Other versions6 projects use a version of this.
Word for word · 2
- harrychuang/cursor-skills★ 19100% same
- PsychQuant/claude-hot-limit★ 0100% same
Edited · 4
- DanSnow/hoarder-pipette★ 9822% same
- PsychQuant/che-ical-mcp★ 4599% same
- BananaBay69/claude-code-watchdog★ 2100% same
- leoho0722/naver-blog-image-downloader★ 2100% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- spectra-analyzeSkill
- spectra-applySkill
- spectra-askSkill
- spectra-auditSkill
- spectra-commitSkill
- spectra-debugSkill
- spectra-discussSkill
- spectra-driftSkill
- spectra-ingestSkill
- spectra-proposeSkill
- spectra-verifySkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. 8 are common, 1 is distinctive, and 8 are very specific to this project.
8
Common
Most of the 4 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 22
Run spectra list --json to get available changes.
- Common: line 27
IMPORTANT: Do NOT guess or auto-select a change.
- Very specific: line 31
Run spectra status --change "<name>" --json to check artifact completion.
- Very specific: line 44
Read the tasks file (typically tasks.md) to check for incomplete tasks.
- Very specific: line 57
Check for delta specs at openspec/changes/<name>/specs/.
- Common: line 65
If changes needed: "Sync now (recommended)", "Archive without syncing"
- Common: line 66
If already synced: "Archive now", "Sync anyway", "Cancel"
- Common: line 68
If user chooses sync, use Task tool (subagent_type: "general-purpose", prompt: "Use Skill tool to invoke spectra-sync-specs for change …
- Very specific: line 72
Delete .spectra/touched/<change-name>.json if it exists.
- Distinctive: line 78
If the file does not exist, silently continue.
- Very specific: line 82
Use the spectra archive CLI command which handles the full archive workflow (spec snapshot, delta application, @trace injection, identity …
- Common: line 167
Always prompt for change selection if not provided
- Very specific: line 168
Use artifact graph (spectra status --json) for completion checking
- Common: line 169
Don't block archive on warnings - just inform and confirm
- Very specific: line 172
If sync is requested, use the Skill tool to invoke spectra-sync-specs (agent-driven)
- Common: line 173
If delta specs exist, always run the sync assessment and show the combined summary before prompting
- Common: line 174
If AskUserQuestion tool is not available, ask the same questions as plain text and wait for the user's response
“Common” is measured: kept by at least 6 in 10 of the 4 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.
Files
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
If no change name provided, prompt for selection
Run
spectra list --jsonto 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.
Check artifact completion status
Run
spectra status --change "<name>" --jsonto check artifact completion.Parse the JSON to understand:
schemaName: The workflow being usedartifacts: List of artifacts with their status (doneor other)
If any artifacts are not
done:- Display warning listing incomplete artifacts
- Prompt user for confirmation to continue
- Proceed if user confirms
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.
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.- Compare each delta spec with its corresponding main spec at
Clean up tracking file
Delete
.spectra/touched/<change-name>.jsonif it exists. This file contains implementation tracking data that is not needed after archiving.rm -f .spectra/touched/<change-name>.jsonIf the file does not exist, silently continue.
Perform the archive
Use the
spectra archiveCLI 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.
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 archiveGuardrails
- 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
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
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.

