archive-strategy
Design the archive layer that keeps current workspaces lean without losing history — what moves, when, to where, findable-by-search, with the project-close ritual that makes archiving automatic instead of aspirational. Use when asked set up an archiving system, our workspace is drowning in old projects, when should things get archived, or make history findable without cluttering today. Produces the archive triggers, the destination structure, the findability rules, and the close-out ritual.
npx skills add mohitagw15856/pm-claude-skills --skill archive-strategy --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Archive Strategy Skill Workspaces drown not in bad files but in *finished* ones — closed projects, past years, shipped versions — all cluttering the space where current work lives, because "archive" was never defined as an action with a trigger. A working archive strategy answers four questions structurally: *when* does something move (triggers, not judgment calls), *where* (a parallel dated structure, not a junk room), *how is it found* (search + a skeleton index, not browsing), and *who moves it* (the close-out ritual, so archiving happens at natural endings instead of never). ## What This Skill Produces - **The triggers** — the events that move material to archive automatically: project close, year end, version supersession, person departure - **The destination structure** — `_archive/[year]/[original-path]` mirroring, so provenance survives the move - **The findability layer** — search-first retrieval + the one-page archive index for the things search misses - **The close-out ritual** — the 20-minute end-of-project checklist where archiving actually happens ## Required Inputs Ask for these if not provided: - **The workspace(s)** — drive, project tool, wiki, or all three; each
- What This Skill Produces
- Required Inputs
- Framework: The Strategy Rules
- Output Format
- The Triggers
- The Destination
- Findability
- The Close-Out Ritual (20 min, attached to [the existing close event])
- Quality Checks
- Anti-Patterns
What does the archive-strategy skill do?
Design the archive layer that keeps current workspaces lean without losing history — what moves, when, to where, findable-by-search, with the project-close ritual that makes archiving automatic instead of aspirational. Use when asked set up an archiving system, our workspace is drowning in old projects, when should things get archived, or make history findable without cluttering today. Produces the archive triggers, the destination structure, the findability rules, and the close-out ritual.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill archive-strategy --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.