archive

Archive active Loom sessions and related plan files to docs/loom directories.

2|Updated Apr 4, 2026

Search Tags:#workflow #backup #archive #traceability #session #state #loom

Ready to run

npx skills add https://github.com/Nickalus12/Loom --skill archive-nickalus12

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: archive
Source: https://github.com/Nickalus12/Loom/tree/main/claude/skills/archive
Command: npx skills add https://github.com/Nickalus12/Loom --skill archive-nickalus12

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive the active Loom session while preserving the shared state layout to enable clean rollbacks and future reference.

Core Features & Use Cases

Safely move the current session to an archive location without deleting related design and implementation artifacts.
Maintain the existing directory structure to ensure traceability of archived sessions and associated plans.
Use case: When preparing for project handoffs or post-mortems, snapshot the active state and associated plans for archival.

Quick Start

Archive the active Loom session by moving it to the archive directory while preserving the shared state layout.

Frequently Asked Questions about archive

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

FAQPage Schema

How do I archive a Loom session without losing shared state and design plans?▼

To archive a Loom session without losing state, move the session file to docs/loom/state/archive/ and relocate related design and implementation plan files to docs/loom/plans/archive/, ensuring traceability and preserved history.

What is the best way to preserve traceability across archived Loom folders during project handoffs?▼

Preserving traceability across archived Loom folders during handoffs requires safely moving the active session and related plans to their respective archive directories while maintaining the existing directory structure for future reference.

Does archiving an active Loom session delete related design and implementation artifacts?▼

Archiving an active Loom session does not delete related design and implementation artifacts; it relocates them to docs/loom/plans/archive/ to maintain the shared state layout and ensure clean rollbacks.

How do I validate that no active Loom session file remains after archiving?▼

To validate that no active Loom session file remains after archiving, ensure the session file is moved to docs/loom/state/archive/ and confirm that history is preserved without leaving active-session files behind.

When should I archive an active Loom session for post-mortems or rollbacks?▼

You should archive an active Loom session for post-mortems or rollbacks when you need to snapshot the active state and associated plans, ensuring the shared state layout is preserved without loss of design or implementation plans.

Can I restore an archived Loom session and its associated plans?▼

Restoring an archived Loom session and its associated plans is supported by maintaining the existing directory structure in docs/loom/state/archive/ and docs/loom/plans/archive/, enabling clean rollbacks and future reference.