archive-work

Archive scratchpad and session log files into timestamped folders with git mv.

1|Updated Dec 28, 2025
One-click install
npx skills add https://github.com/fusupo/escapement --skill archive-work
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: archive-work
Source: https://github.com/fusupo/escapement/tree/main/skills/archive-work
Command: npx skills add https://github.com/fusupo/escapement --skill archive-work

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed scratchpads and session logs to preserve project history while keeping the working tree clean.

Core Features & Use Cases

  • Move scratchpad artifacts from the project root into a timestamped archive folder.
  • Preserve session logs for traceability and post-mortem review after PRs.
  • Generate a concise README summary in each archive to document decisions and outcomes.

Quick Start

Trigger the archive workflow after finalizing a task. The skill locates SCRATCHPAD_.md and SESSION_LOG_.md, moves them to docs/dev/cc-archive/{timestamp}-{issue}-{description}/, creates a SUMMARY README, and optionally commits the archive.

Frequently Asked Questions about archive-work

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

FAQPage Schema
How do I archive scratchpad files and session logs after completing a task?

To archive scratchpad files, trigger the workflow to locate SCRATCHPAD_*.md and SESSION_LOG_*.md files, then use git mv to move them into a timestamped folder under docs/dev/cc-archive. This preserves project history while keeping your working tree clean.

What is the best way to preserve project history from scratchpad-driven workflows?

The best way to preserve project history is archiving artifacts into a structured timestamped directory. This process moves completed task files and generates a README summary documenting decisions and outcomes for post-mortem traceability.

Does archiving scratchpad artifacts use git mv to track file movements?

Yes, archiving scratchpad artifacts uses git mv to track file movements. This ensures the relocation of session logs and task files into the timestamped archive folder is recorded in version control history.

Can I generate a summary README automatically when archiving session logs?

Yes, you can generate a summary README automatically when archiving session logs. The archiving process creates a concise README in the docs/dev/cc-archive folder to document project decisions and outcomes.

When should I archive scratchpad tasks in my software project workflow?

You should archive scratchpad tasks after finalizing a task or completing a PR process. Archiving at this stage ensures session logs and artifacts are preserved for traceability before the working tree is cleared for new development.

What limitations exist when archiving scratchpad artifacts into a timestamped folder?

A limitation is that archiving scratchpad artifacts requires a specific file naming convention, targeting only SCRATCHPAD_*.md and SESSION_LOG_*.md files. Files not matching this pattern in the project root will not be included in the timestamped archive folder.