archive-project

Condenses a completed project directory into a single archived README with promoted decisions and rewritten cross-references.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/mikestopcontinues/agent-skills --skill archive-project-mikestopcontinues
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: archive-project
Source: https://github.com/mikestopcontinues/agent-skills/tree/main/claude/skills/archive-project
Command: npx skills add https://github.com/mikestopcontinues/agent-skills --skill archive-project-mikestopcontinues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finished projects leave behind sprawling directories of spikes, plans, decisions, and notes that clutter the docs workspace. This Skill condenses a completed project into one archived README while preserving important decisions and follow-up work in top-level locations, all as a single recoverable git commit. ## Core Features & Use Cases - Decision promotion: Walks each project decision with the captain and promotes cross-cutting ones to top-level docs/decisions/ with preserved slugs and frontmatter. - Follow-up relocation: Moves open notes and unchecked tasks into docs/notes/ or drops them with per-item captain approval. - Cross-reference rewriting: Rewrites Markdown links and frontmatter source fields across all of docs/ according to the promotion mapping, surfacing orphans for captain decision. - Safe deletion: Validates the condensed README via a single-pass /validate-doc loop and requires explicit captain confirmation before any source content is deleted, then lands everything in one atomic git commit recoverable via git revert. - Use Case: After finishing project x003-auth-redesign, run the archive flow to promote two reusable decisions to docs/decisions/, move one open note, rewrite inbound links, and commit a single condensed README. ## Quick Start Ask the agent to archive project x003-auth-redesign using the archive-project skill and confirm each decision promotion when prompted.

Frequently Asked Questions about archive-project

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

FAQPage Schema
How do I archive a completed project in a docs workspace?▼

Invoke the archive flow with the project id, such as /archive-project x003-auth-redesign. The skill condenses the project into one README, promotes approved decisions to docs/decisions/, moves follow-up to docs/notes/, rewrites inbound links, and commits everything atomically.

How does the skill prevent losing project content during archival?▼

Source files are never deleted until the condensed README passes a single-pass /validate-doc review and the captain explicitly confirms deletion. Everything lands in one git commit, so full recovery is a single git revert of that commit.

Can I batch-promote all important decisions automatically?▼

No. Every decision promotion requires individual captain approval; the skill walks decisions oldest to newest and asks whether to promote each one or summarize it in the README. Batch promotion is explicitly forbidden.

What happens to links pointing at the archived project?▼

Markdown links and frontmatter source fields across all of docs/ are rewritten according to the promotion mapping table. Bare prose mentions are left untouched, and any orphan references are surfaced to the captain for a per-item decision.

When should I not use archive-project?▼

Do not use it while a project is still in flight, when you want outright deletion with no historical record, or on an already-archived project. For an archived project, run git revert of the archive commit first before re-archiving.