10x-archive

Archives completed change folders into context/archive with git history preservation and roadmap closure.

Updated May 20, 2026
One-click install
npx skills add https://github.com/Oskarovsky/Sprinter --skill 10x-archive-oskarovsky
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 10x-archive
Source: https://github.com/Oskarovsky/Sprinter/tree/main/.cursor/skills/10x-archive
Command: npx skills add https://github.com/Oskarovsky/Sprinter --skill 10x-archive-oskarovsky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Completed change folders accumulate in context/changes/ and clutter the active workspace, while manually moving them loses git history and leaves roadmap items stale. This Skill closes a change cleanly by moving its folder, stamping its metadata, and updating the roadmap in one commit. ## Core Features & Use Cases - History-preserving move: Relocates context/changes/<change-id>/ to context/archive/<created-date>-<change-id>/ using git mv so file history follows the rename. - Lenient warn-only gate: Hard-blocks only on uncommitted changes or pre-existing staged files; incomplete Progress items, missing impl-reviews, and unexpected statuses surface as warnings with a confirmation prompt. - Roadmap closure: When context/foundation/roadmap.md contains an item whose Change ID matches, flips its Status to done and appends an entry to the ## Done section, all staged into the same archive commit. - Use Case: After finishing and reviewing the oauth-login change, run the archive command to move its folder, stamp change.md with status archived and archived_at, close the matching roadmap slice, and commit everything as chore(archive): close oauth-login. ## Quick Start Archive the completed change oauth-login by moving its folder to context/archive and closing its roadmap item.

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 git?

Provide the change-id or path as an argument, and the folder moves from context/changes/<change-id>/ to context/archive/<created-date>-<change-id>/ via git mv. The change.md frontmatter is stamped with status archived and archived_at, then everything lands in one chore(archive) commit.

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 warning you can override.

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 after mkdir -p context/archive. You lose history preservation and the automatic archive commit, but the move and stamping still complete.

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 in the table and body, appends a ## Done entry, and stages it into the archive commit unless the roadmap already had uncommitted edits.

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.