10x-archive

Move completed change folders to an archive directory and update related documents.

Updated May 17, 2026
One-click install
npx skills add https://github.com/yakksiek/car-rental --skill 10x-archive-yakksiek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 10x-archive
Source: https://github.com/yakksiek/car-rental/tree/main/.claude/skills/10x-archive
Command: npx skills add https://github.com/yakksiek/car-rental --skill 10x-archive-yakksiek

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill simplifies the process of archiving completed changes by moving folders to an archive directory and updating related documents, making it easy to organize and track completed work.

Core Features & Use Cases

  • Automated Archive: Move completed change folders to an archive directory, preserving file history and context.
  • Update Documents: Update the change.md file with archived status and close related roadmap items if applicable.
  • Use Case: Use this Skill to archive a completed feature development change, ensuring all related documentation and tracking are updated in one step.

Quick Start

Archive a completed change by providing the change ID or path to 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 completed change folders and update roadmap items automatically?

To archive completed change folders and update roadmap items, you can use a script that moves the directories to an archive location, modifies the change.md file to reflect archived status, and closes the matching roadmap entries while preserving Git history.

What is the best way to organize completed change documentation in Git without losing file history?

Organizing completed change documentation in Git requires moving folders to an archive directory while updating related tracking documents. This approach preserves file history and context, ensuring completed work is cleanly separated from active changes.

How do I update change.md files with archived status when moving project folders?

Updating change.md files with archived status involves moving the completed change folder to an archive directory and modifying the document text to reflect the new archived state, ensuring documentation accurately tracks the project lifecycle.

Do I need Git access to close roadmap items and archive change management folders?

Yes, you need Git access to archive change management folders and close roadmap items. Git is required to preserve file history and context when moving completed change directories to the archive location.

Can I batch archive multiple completed feature development changes at once?

The archiving process applies to change management workflows by moving completed change folders to an archive directory and closing related roadmap items. You provide the specific change ID or path to initiate the archival process.