What is spec-archive?

A workflow for moving a completed software specification from an active work folder into a documentation archive. A specification is a written description of what should be built and how it should work.

Use it after all tasks are checked off and verification has passed to archive the spec, add completion metadata, and update its index.

It keeps finished specifications organized and records that they were verified and implemented.

How sourjya/kiro-rails configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to sourjya/kiro-rails. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/sourjya/kiro-rails/main/.claude/skills/spec-archive/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/sourjya/kiro-rails

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/sourjya/kiro-rails/spec-archive/github.svg)](https://agentmods.dev/skills/sourjya/kiro-rails/spec-archive)

Your own site

<a href="https://agentmods.dev/skills/sourjya/kiro-rails/spec-archive"><img src="https://agentmods.dev/badge/skills/sourjya/kiro-rails/spec-archive/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/sourjya/kiro-rails/spec-archive"><img src="https://agentmods.dev/badge/skills/sourjya/kiro-rails/spec-archive.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 443 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00033	$0.00443
Opus 5	$0.00016	$0.00221
Sonnet 5	$0.00007	$0.00089
Haiku 4.5	$0.00003	$0.00044

Measured 10d ago against content hash da9d763bd1df, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

spec-archive scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/spec-archive/SKILL.md · 67 lines

What it actually says

Spec Archive Workflow

Archive a completed spec after it passes verification.

Steps

Verify completion - all tasks checked, verification passed
Move to archive - relocate from .kiro/specs/<name>/ to docs/architecture/specs/<name>/
Update registry - add entry to the spec index
Clean up - remove the active spec folder

Process

1. Pre-Archive Check

Confirm in tasks.md:

All - [ ] are now - [x]
Verification Results section exists with status ✅ PASSED

If not, inform the user and suggest running spec-verify first.

2. Archive Location

Move the entire spec folder:

.kiro/specs/<feature-name>/  →  docs/architecture/specs/<feature-name>/

Create docs/architecture/specs/ if it doesn't exist.

3. Add Archive Metadata

Prepend to the archived proposal.md:

---
archived: YYYY-MM-DD
status: completed
implemented-in: <branch or commit reference>
---

4. Update Spec Index

Append to docs/architecture/specs/INDEX.md (create if missing):

| <Feature Name> | YYYY-MM-DD | Completed | Brief description |

5. Clean Up

Remove .kiro/specs/<feature-name>/ (it now lives in docs)
Inform the user the spec is archived

Rules

Never archive a failing spec - verification must pass first
Preserve history - the archive is the source of truth for "what was built and why"
Link to implementation - include branch/commit/PR reference in metadata
Keep the index current - every archived spec must appear in INDEX.md

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

10d ago First seen · 67 lines · 33 tokens per session scan A da9d763bd1df

Subscribe to this mod's changes

spec-archive is a skill published in the GitHub repository sourjya/kiro-rails (9 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 443 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Writing and docs

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

kiro-rails: Skill for Claude Code