spec-archive SKILL.md skillA

spec-archive from kamioj/spec-workflow is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add kamioj/spec-workflow/spec-archive@git:20260921.886d28d

Pins git:20260921.886d28d in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: kamioj/spec-workflow
Path: codex/skills/spec-archive/SKILL.md
Versions recorded: 6
Latest version: git:20260921.886d28d, committed Sep 21, 2026
First version recorded: Jul 14, 2026
Size: 7,523 bytes
Repository stars: 20
License: a license file GitHub does not identify

Archives the current change to spec/archive/YYYY-MM-DD-<name>/. Only invoked when the user explicitly says "archive". Writes an archive-stage retrospect, checks for uncommitted code, and is guarded by the check-archive hook.

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

<!-- GENERATED from core/commands/archive.md — edit the core file and run node tools/generate.mjs; hand edits will be overwritten -->

# $spec-archive

## Pre-flight checks

0. **Hook layer**: `codex/hooks/check-archive` has already screened this invocation — it blocks (outputs `{"decision":"block"}` to stdout) when the change bypassed the flow: proposal.md without the APPROVED marker / tasks.md with unchecked items / no proposal.md at all. Deliberate override: the user says `force` (archive as-is) or `abandoned` (drop the direction). When an override passed through, the reason **MUST be recorded in retrospect.md** (Process step 2).
1. **git status check**:
   - Uncommitted changes present → warn the user and ask "commit first or archive first?"
   - User chooses "archive first" → proceed; "commit first" → exit and prompt the user to run `git commit`
2. **Verification status**: read `spec/changes/<name>/verify.md` (the verification ledger) — latest round's `conclusion` + open findings
   - Recommended: `conclusion: pass` with zero open critical/major findings before archiving
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add kamioj/spec-workflow/spec-archive@sha256:e66e2a12e10bf252

The line at the top of this page pins the label git:20260921.886d28d, 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.

Badge

[![mdr](https://markdownregistry.com/badge/art_njkcud5xwtoqjok4.svg)](https://markdownregistry.com/a/art_njkcud5xwtoqjok4)

5 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 6 versions of this file, between Jul 14, 2026 and Sep 21, 2026, about one every 14 days.

version	committed	commit	size	audit
git:20260921.886d28d latest	2026-09-21	886d28d	7,523 B	A	view · diff
git:20260910.a57f970	2026-09-10	a57f970	7,201 B	A	view · diff
git:20260804.97502e3	2026-08-04	97502e3	6,254 B	A	view · diff
git:20260717.6ee7a9c	2026-07-17	6ee7a9c	5,940 B	A	view · diff
git:20260717.4ff32bc	2026-07-17	4ff32bc	5,704 B	A	view · diff
git:20260714.a0e0c5f	2026-07-14	a0e0c5f	5,474 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (7523 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag

Source

GitHub

kamioj/spec-workflow · 20 stars · license a license file GitHub does not identify · pushed 2026-09-21 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_njkcud5xwtoqjok4
GET https://markdownregistry.com/api/v1/resolve?ref=kamioj/spec-workflow/spec-archive
GET https://markdownregistry.com/api/v1/blob/e66e2a12e10bf25239448468d1674150b0847084d376510a301c4250eed82788

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.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.