archive-project
Archive a completed project by creating an AI-generated summary in Knowledge/, storing the git commit hash for reference, and deleting the original project file. Use when user says a project is "done", "complete", "finished", or wants to "archive" it.
Best use case
archive-project is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Archive a completed project by creating an AI-generated summary in Knowledge/, storing the git commit hash for reference, and deleting the original project file. Use when user says a project is "done", "complete", "finished", or wants to "archive" it.
Teams using archive-project should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/archive-project/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How archive-project Compares
| Feature / Agent | archive-project | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Archive a completed project by creating an AI-generated summary in Knowledge/, storing the git commit hash for reference, and deleting the original project file. Use when user says a project is "done", "complete", "finished", or wants to "archive" it.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Archive Project Archive a completed project to preserve its knowledge while cleaning up the Projects/ folder. ## Instructions When the user wants to archive a project: ### 1. Identify the Project File - If not specified, ask which project to archive - List projects in the relevant pillar: `ls [Pillar]/Projects/` - Confirm the file path (e.g., `Personal/Projects/Some Project.md`) ### 2. Get Current Git State ```bash git rev-parse HEAD git log -1 --format="%H %s" ``` Store the commit hash - this is the reference point for restoration. ### 3. Read and Summarise the Project Read the project file and create an intelligent summary covering: - **What the project was about** - goals, context, purpose - **Key outcomes and learnings** - what was achieved, lessons learned - **Important decisions made** - architectural choices, trade-offs, rationale ### 4. Create Archived Summary Create a new file at `[Pillar]/Knowledge/[Project Name] (Archived).md`: ```markdown # [Project Name] (Archived) Archived: YYYY-MM-DD Commit: `[hash]` ## Summary [AI-generated summary of what the project was about, its goals, and context] ## Outcomes & Learnings [AI-generated summary of key outcomes, what was achieved, lessons learned] ## Key Decisions [AI-generated list of important decisions made during the project] ## Reference To restore or view the original project: ```bash git show [hash] git checkout [hash] -- "[Pillar]/Projects/[Project Name].md" ``` #type/archive #context/[pillar] ``` ### 5. Update Manifest Add entry to `[Pillar]/Knowledge/MANIFEST.md`: - If the auto-update hook is configured, this happens automatically - Otherwise, manually add the new file to the manifest table ### 6. Delete Original Project ```bash rm "[Pillar]/Projects/[Project Name].md" ``` The knowledge is now preserved in the archived summary. ### 7. Commit Changes ```bash git add -A git commit -m "Archive project: [Project Name]" ``` ## Example User: "The Marketing Campaign project is done, archive it" Steps: 1. Read `Personal/Projects/Marketing Campaign.md` 2. Get commit hash: `abc123def` 3. Create AI-generated summary at `Personal/Knowledge/Marketing Campaign (Archived).md` 4. Manifest updates automatically (hook) or manually 5. Delete `Personal/Projects/Marketing Campaign.md` 6. Commit: "Archive project: Marketing Campaign" ## Notes - Always get the commit hash BEFORE making any changes - The archived summary should be comprehensive enough to understand the project without the original file - The commit hash allows full restoration if needed via `git checkout`
Related Skills
ck:project-management
Track progress, update plan statuses, manage Claude Tasks, generate reports, coordinate docs updates. Use for project oversight, status checks, plan completion, task hydration, cross-session continuity.
audit-and-add-project-skills
Audits project skills in .agent/skills/ and Codex skills for Cursor compatibility, then helps add compatible skills to .cursor/skills/. Use when the user wants to migrate project skills to Cursor, check if skills work with Cursor, or add existing skills to Cursor.
agent-project-manager
Expert project manager specializing in project planning, execution, and delivery. Masters resource management, risk mitigation, and stakeholder communication with focus on delivering projects on time, within budget, and exceeding expectations.
writing-project-technical-writing
Writes technical prose (READMEs, ADRs, code comments) in the project's established human voice. Use when creating or editing .md files, writing Swift doc comments, authoring ADRs, or reviewing technical writing for voice consistency.
Project Setup and CCAGI Integration
Complete project initialization including Node.js/TypeScript setup, GitHub integration, and CCAGI framework integration. Use when creating new projects or integrating CCAGI components.
gsd:workflow:resume-project
Workflow for resuming a paused project
github-archive
Investigate GitHub security incidents using tamper-proof GitHub Archive data via BigQuery. Use when verifying repository activity claims, recovering deleted PRs/branches/tags/repos, attributing actions to actors, or reconstructing attack timelines. Provides immutable forensic evidence of all public GitHub events since 2011.
archive
Archive completed task/spec work to ./.gtd/archive/
archive-work
Archive completed scratchpads and session logs to project history. Invoke when user says "archive this work", "clean up scratchpad", "archive scratchpad", or after PR is merged.
archive-ticket
Archive completed tickets by moving them to .archived/
archive-plan
Archive completed plan documents by moving them to the plans/archived folder. Use when a plan has been fully implemented, all to-do items are completed, or when the user requests to archive a plan.
archive-increments
Intelligent increment archiving expert that analyzes age, status, and activity to recommend archiving. Use when workspace has too many increments, cleaning up completed work, or organizing the _archive folder. Follows the 10-10-10 rule for workspace organization.