archive

Archive the most recent blueprint file to archive/ and commit the change.

8|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/jfmyers9/agent --skill archive-jfmyers9
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: archive
Source: https://github.com/jfmyers9/agent/tree/main/skills/archive
Command: npx skills add https://github.com/jfmyers9/agent --skill archive-jfmyers9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive blueprint files to the archive/ directory and commit the change to keep historical plans organized and prevent clutter.

Core Features & Use Cases

  • Archive the most recent blueprint file to archive/ or a specified target.
  • Commit the change to version control to ensure traceability.
  • Triggered by commands like /archive or "archive this blueprint" to clean up active work streams.

Quick Start

Archive the most recent blueprint file to archive/ and commit.

Frequently Asked Questions about archive

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I archive blueprint files and keep historical plans organized?

Archiving blueprint files involves moving them to an archive directory and committing the change to version control. This ensures historical plans stay organized and prevents active work streams from becoming cluttered.

What is the best way to move the most recent plan file into an archive directory?

Moving the most recent plan file into an archive directory is handled by targeting the newest blueprint and relocating it automatically. The process applies deterministic archiving to ensure the exact file is moved and committed properly.

Can I specify a target blueprint file to archive instead of the most recent one?

Specifying a target blueprint file to archive is supported alongside the most recent item. The archiving mechanism handles both a user-specified target and the default newest file, moving either into the archive directory with proper error handling.

Does archiving blueprint files automatically commit the change to version control?

Archiving blueprint files automatically commits the change to version control. This ensures traceability for the relocation event, keeping the repository history aligned with the physical file movement to the archive directory.

What happens if a blueprint file fails to archive correctly?

If a blueprint file fails to archive correctly, the process provides clear feedback on the failure. Deterministic archiving with proper error handling ensures you are notified of success or failure rather than silently dropping the operation.