skills.rest
ninthspace
ninthspaceCOMMUNITY
Explore all skills by this author →
𝕏@ninthspaceGitHub

cpm:archive

Scan planning directories and archive stale documents after user confirmation.

Updated Oct 11, 2025
Search Tags:#workflow#planning#archive#docs#state-management#chains#user-confirmation
One-click install
npx skills add https://github.com/ninthspace/claude-code-marketplace --skill cpm-archive
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cpm:archive
Source: https://github.com/ninthspace/claude-code-marketplace/tree/main/cpm/skills/archive
Command: npx skills add https://github.com/ninthspace/claude-code-marketplace --skill cpm-archive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive old or completed planning documents to keep active docs/ clean while preserving history. This skill scans planning directories, groups artifacts into chains, and moves them to docs/archive/ only after user confirmation, ensuring traceability and recoverability.

Core Features & Use Cases

  • Scan planning directories (docs/plans, docs/specifications, docs/epics, docs/retros) to discover artifact candidates while excluding library directories.
  • Group related documents into artifact chains by slug and, when applicable, associate epics with their source specifications to reflect multi-doc relationships.
  • Archive non-destructively by moving files to docs/archive/ while preserving the original directory structure, and require explicit user confirmation before any move.
  • Maintain a CPM session state during the operation to enable safe resumption if context is interrupted.

Quick Start

Review and select artifact chains to archive; the tool will move matched files to docs/archive while preserving history.

Frequently Asked Questions about cpm:archive

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

FAQPage Schema
How do I safely archive completed planning documents without losing history?▼

Archive planning documents safely by moving completed files to docs/archive while preserving the original directory structure. This non-destructive process mirrors paths from docs/plans, docs/specifications, docs/epics, and docs/retros, ensuring traceability and recoverability.

What is the best way to group related specification and epic files before archiving?▼

Group related specification and epic files by slug to form artifact chains before archiving. Scanning planning directories discovers candidates and associates epics with source specifications to reflect multi-doc relationships accurately.

Can I resume document archiving if my workflow session is interrupted?▼

Resume document archiving safely after an interruption by maintaining a CPM session state. This state management mechanism tracks stepwise progress, allowing the archiving workflow to continue without losing context.

Does the archiving process require explicit user confirmation before moving files?▼

The archiving process requires explicit user confirmation before moving any files. You review and select artifact chains, ensuring safe non-destructive moves that only execute after you approve the relocation to docs/archive.

Which planning directories are scanned for stale document candidates?▼

Planning directories scanned for stale document candidates include docs/plans, docs/specifications, docs/epics, and docs/retros. Library directories are excluded during the discovery process to focus only on active planning artifacts.

Related Skills

Explore More Product & Management Skills→
gaiastudio-aigaiastudio-ai
2

gaia-create-story

Convert epics and stories into documented artifacts with YAML frontmatter and acceptance criteria.

Official
Intermediate
Nickalus12Nickalus12
2

archive

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

Community
Intermediate
plurigridplurigrid
60

file-organizer

Analyze directory contents, identify duplicates, and propose folder structures.

Official
Intermediate
brainsnorkelbrainsnorkel

openspec-archive-change

Archive completed changes in the experimental workflow via the openspec CLI.

Community
Advanced