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/ZawilecxD/trAInR --skill 10x-archive-zawilecxd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 10x-archive
Source: https://github.com/ZawilecxD/trAInR/tree/main/.cursor/skills/10x-archive
Command: npx skills add https://github.com/ZawilecxD/trAInR --skill 10x-archive-zawilecxd

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 or pre-staged changes; incomplete progress, missing impl-reviews, and unexpected status 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, staged into the same archive commit. - Use Case: After finishing and reviewing an oauth-login change, run the archive command to move the 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 Ask the assistant to archive the completed change by running /10x-archive with your change-id, for example /10x-archive oauth-login.

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?

Run /10x-archive with the 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 status archived, and commits the result.

What blocks the 10x-archive command from running?

Only two hard blocks exist: uncommitted changes inside the change folder, and pre-existing staged changes anywhere in the repo that would be bundled into the archive commit. All other issues like pending progress items or missing reviews are warnings you can override.

Does archiving a change update the roadmap automatically?

Yes, if 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 bullet to the ## Done section, and stages it into the same commit when the file was clean.

Can I archive a change without git installed?

Yes. The skill prints a warning and falls back to a plain mv into context/archive/, skipping the archive commit. You lose git history preservation on the rename, but the folder move and change.md stamping still complete.

What happens if archiving fails partway through?

The change.md stamp is applied before the move, so a partial failure leaves status archived in the original folder. Re-running the command detects this state and asks you to inspect manually; no automatic rollback is attempted.