Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
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.
…
The line at the top of this page pins the label v1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_tihinfzxa2fjgqsa
GET https://markdownregistry.com/api/v1/resolve?ref=tekkiiiii/the-agency/openspec-archive-change
GET https://markdownregistry.com/api/v1/blob/e111d71216167eea10cec26abe8f6e15d925efeef2fd9925ffa219f55145acce
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
tekkiiiii/the-agency · agents-archive/dept-sunset-2026-10-08/skills/dept-resume/SKILL.md · Read dept-state.md and spawn a Dept Head with a lean briefing. Department-operations parallel of /pd-resume.
tekkiiiii/the-agency · agents-archive/dept-sunset-2026-10-08/skills/dept-save-state/SKILL.md · Write dept-state.md and member-roster.md at end of department session. Department-operations parallel of /save-state.
tekkiiiii/the-agency · agents-archive/dept-sunset-2026-10-08/skills/dept-status/SKILL.md · Read-only department status digest. No spawns. Shows active coords, pipelines, open issues, and incoming tasks.
tekkiiiii/the-agency · agents-archive/dept-sunset-2026-10-08/skills/room-manager-digest/SKILL.md · Use on /room-manager-digest, a 12h cron, or when a dept head wants a fresh report. Reads each dept room's rolling.md…
tekkiiiii/the-agency · agents-archive/dept-sunset-2026-10-08/skills/room-manager/SKILL.md · Use on /room-manager, every 10 minutes as a background loop, or when new room activity is suspected (handoff file…
tekkiiiii/the-agency · agents-archive/rev001-curator-2026-10-12/skills/obsidian-vault/SKILL.md · Use to forward decisions, project learnings, skill creations and generated assets to the Obsidian vault, and to read it…
tekkiiiii/the-agency · scripts/tests/fixtures/jev/router-skills/content-polish/SKILL.md · Polish drafted content to publish-ready in one pass; English and Vietnamese.
tekkiiiii/the-agency · scripts/tests/fixtures/jev/router-skills/frontend/SKILL.md · Use when building frontend UIs: "build a landing page", "make a dashboard", "write a React component". Not for…
monid-ai/monid · .opencode/skills/openspec-archive-change/SKILL.md · Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after…
mememeow-studio/mememeow · .opencode/skills/openspec-archive-change/SKILL.md · Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after…
mememeow-studio/mememeow · .claude/skills/openspec-archive-change/SKILL.md · Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after…
mememeow-studio/mememeow · .agents/skills/openspec-archive-change/SKILL.md · Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after…
partcad/partcad · .cursor/skills/openspec-archive-change/SKILL.md · Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after…
partcad/partcad · .claude/skills/openspec-archive-change/SKILL.md · Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after…
asymmetric-al/core · .agents/skills/openspec-archive-change/SKILL.md · Archive a completed OpenSpec change in the experimental workflow. Use when the user wants to finalize and archive a…
intent-driven-dev/intent-driven-template · .opencode/skills/openspec-archive-change/SKILL.md · Archive a completed OpenSpec change in the experimental workflow. Use when the user wants to finalize and archive a…