10x-archive

Archives completed change folders into context/archive with git mv and frontmatter stamping.

Updated Jul 4, 2026
One-click install
npx skills add https://github.com/Assamir/ai-toolkit --skill 10x-archive-assamir
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 10x-archive
Source: https://github.com/Assamir/ai-toolkit/tree/main/.cursor/skills/10x-archive
Command: npx skills add https://github.com/Assamir/ai-toolkit --skill 10x-archive-assamir

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Closing out a finished change in a context-driven workflow requires moving folders, updating frontmatter, preserving git history, and closing roadmap items — doing this by hand is error-prone and easy to forget. This Skill automates the entire archival ritual with safety gates. ## Core Features & Use Cases - History-preserving move: Relocates context/changes/<change-id>/ to context/archive/<created-date>-<change-id>/ using git mv, then stamps change.md with status: archived, archived_at, and updated fields in a single commit. - Lenient warn-only gate: Hard-blocks only on uncommitted changes or pre-existing staged files; surfaces soft warnings for pending Progress items, missing impl-reviews, and SHA-less rows with a confirmation prompt. - Roadmap closure: Automatically flips the matching roadmap item's Status to done and appends an entry to the ## Done section when a Change ID match exists. - Use Case: After finishing and reviewing the oauth-login change, run the archive command to move its folder into the archive, stamp its metadata, close the linked roadmap slice, and commit everything as chore(archive): close oauth-login. ## Quick Start Archive the completed change by telling the AI: archive the change oauth-login using the 10x-archive skill.

Frequently Asked Questions about 10x-archive

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I archive a completed change folder in a context-driven workflow?

Invoke the archive command with a change-id, such as /10x-archive oauth-login. The skill moves context/changes/<change-id>/ to context/archive/<created-date>-<change-id>/ using git mv, stamps change.md with archived status, and commits the result.

What blocks archiving a change folder?

Only two hard blocks exist: uncommitted changes inside the change folder, and pre-existing staged changes anywhere in the repo that would leak into the archive commit. Everything else, like pending Progress items or a missing impl-review, is a warn-only prompt.

Does archiving work without git?

Yes. If git is unavailable or the directory is not a repository, the skill prints a warning and falls back to a plain mv into context/archive. You lose history preservation via git mv and the archive commit step is skipped.

Does archiving update the project roadmap automatically?

Yes, when context/foundation/roadmap.md contains an item whose Change ID exactly matches the archived change. The skill sets its Status to done, appends a bullet to the ## Done section, and stages the edit into the archive commit if the file was clean.

Can I unarchive or modify an archived change folder?

No. Archived folders under context/archive/ are read-only by convention, and all other 10x skills refuse to write into them. To revisit the work, open a new change with /10x-new and reference the archived folder for context.