10x-archive

Archive completed change folders and close linked roadmap items.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the archiving process for completed changes, moving folders to an archive directory and updating related documentation, while also closing corresponding roadmap items.

Core Features & Use Cases

  • Automated Archiving: Moves completed change folders to an archive directory and updates their status.
  • Roadmap Item Closure: Closes roadmap items linked to archived changes.
  • Use Case: When a change is completed, use this Skill to archive the change and update the roadmap, ensuring a clean and organized project history.

Quick Start

Archive a completed change by running the command: /10x-archive <change-id>

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 project changes and close roadmap items?

To archive completed project changes, this Skill automates moving change folders to an archive directory and updates roadmap documentation to close linked items. It ensures a clean project history by handling folder management and roadmap closure together.

What happens to uncommitted changes when archiving a project folder?

When archiving a project folder, the Skill detects uncommitted changes and provides warnings for issues that may prevent successful archiving. This prevents data loss by alerting you to unresolved version control states before moving the folder.

How does automated change archiving work for project organization?

Automated change archiving works by moving completed change folders into a designated archive directory and updating their status. It requires access to project change folders and roadmap documentation to execute the closure process.

Do I need any specific dependencies to automate roadmap closure?

No specific dependencies are required to automate roadmap closure. The Skill operates using internal scripts to manage folder management and roadmap documentation updates, requiring only access to the project's change folders.

What is the best way to maintain a clean project history after completing a change?

The best way to maintain a clean project history is using automated change archiving to move completed folders to an archive directory and close corresponding roadmap items, ensuring organizational documentation stays current.