10x-archive

Move completed change folders into archive and update metadata.

1|Updated Feb 26, 2025
One-click install
npx skills add https://github.com/kryptonum-dev/fabryka-atrakcji --skill 10x-archive
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 10x-archive
Source: https://github.com/kryptonum-dev/fabryka-atrakcji/tree/main/.agents/skills/10x-archive
Command: npx skills add https://github.com/kryptonum-dev/fabryka-atrakcji --skill 10x-archive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of cleaning up completed 10x changes by moving them into an archive location while correctly marking their status and updating related roadmap tracking.

Core Features & Use Cases

  • Closes a completed change: Moves context/changes/<change-id>/ to context/archive/<created-date>-<change-id>/ and updates change.md frontmatter to status: archived, adds archived_at, and updates updated.
  • Preserves history when possible: Uses git mv and stages the stamped change.md into the same commit so rename history follows.
  • Roadmap closure (best effort): Finds a matching item in context/foundation/roadmap.md by exact Change ID, flips it to done, appends an ## Done bullet, and bumps the roadmap updated date when applicable.
  • Guardrails with warning-first behavior: Hard-blocks only on uncommitted edits inside the change folder or on pre-existing staged changes that would be bundled into the archive commit; everything else becomes a warn + confirm flow so archiving can proceed intentionally.

Quick Start

Run /10x-archive context-dir-restructure to archive the completed change folder and mark it archived in its change.md (and close any matching roadmap item when found).

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 while preserving git history?

Archiving a completed change involves relocating its folder from context/changes into context/archive using git mv to preserve history. The tool updates change.md frontmatter to status: archived and stages the metadata file into the same commit.

What happens to my roadmap tracking when I archive a completed change?

Roadmap closure happens automatically as a best-effort update when archiving a change. It finds the exact Change ID in roadmap.md, flips the status to done, appends a Done bullet, and bumps the updated date without rolling back if the match fails.

Can I archive a change if I have uncommitted edits inside the change folder?

Uncommitted in-folder edits or pre-existing staged changes trigger a hard block during the archive process. This prevents bundling untracked modifications into the archive commit, ensuring a clean status transition to archived.

Does the archiving process require a specific change status before it can proceed?

The archiving process validates change status, plan progress, and review presence before proceeding. These act as warn-only soft checks that trigger a confirmation prompt, allowing the user to intentionally proceed with the state transition.

What is the best way to clean up completed changes in a 10x workflow?

Using a consistent post-completion state transition is the best way to clean up completed 10x changes. It relocates the change folder to context/archive, stamps the change.md metadata to archived, and closes matching roadmap items.