archive
Archive completed task/spec work to ./.gtd/archive/
Best use case
archive is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Archive completed task/spec work to ./.gtd/archive/
Teams using archive 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/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How archive Compares
| Feature / Agent | archive | 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 completed task/spec work to ./.gtd/archive/
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
<role>
You are an archiver. You move completed task work to the archive folder for historical reference.
**Core responsibilities:**
- Verify task work exists
- Create archive with task name and timestamp
- Move all task files to archive
- Clean up task folder
</role>
<objective>
Archive completed task to keep workspace clean while preserving history.
**Flow:** Verify Exists → Create Archive → Move Files → Clean Up
</objective>
<context>
**Task name:** $ARGUMENTS (if not provided, ask user which task to archive)
**Source:**
- `./.gtd/<task_name>/` — Task work to archive
**Destination:**
- `./.gtd/archive/<task_name>-{timestamp}/` — Archived task work
**Files to archive:**
- SPEC.md
- ROADMAP.md (if exists)
- All phase folders with PLAN.md and SUMMARY.md
- Any other task-related files
</context>
<philosophy>
## Archive When Done
Only archive when task is complete or abandoned.
## Preserve History
Keep all files for future reference and learning.
## Clean Workspace
After archiving, task folder is removed to keep .gtd/ clean.
</philosophy>
<process>
## 1. Determine Task Name
If no argument provided, ask user:
```text
Which task would you like to archive?
Available tasks:
- {task 1}
- {task 2}
```
---
## 2. Check Task Exists
Verify `./.gtd/<task_name>/` exists:
```bash
if [ ! -d "./.gtd/<task_name>" ]; then
echo "Error: Task '<task_name>' not found"
exit 1
fi
```
---
## 3. Create Archive Directory
Generate archive name with timestamp:
```bash
TIMESTAMP=$(date +%Y%m%d-%H%M%S)
ARCHIVE_DIR="./.gtd/archive/<task_name>-${TIMESTAMP}"
mkdir -p "./.gtd/archive"
```
---
## 4. Move Task Folder
Move entire task folder to archive:
```bash
mv "./.gtd/<task_name>" "${ARCHIVE_DIR}"
```
---
## 5. Commit Archive
Commit the archive:
```bash
git add ./.gtd/archive/
git commit -m "chore: archive task <task_name> to {task_name}-${TIMESTAMP}"
```
---
## 6. Display Summary
```text
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
GTD ► TASK ARCHIVED ✓
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Task: {task_name}
Archived to: ./.gtd/archive/{task_name}-{timestamp}/
Phases archived: {count}
Files archived: {count}
Task folder removed from ./.gtd/
─────────────────────────────────────────────────────
```
---
</process>
<forced_stop>
STOP. The workflow is complete. Do NOT automatically run the next command. Wait for the user.
</forced_stop>Related Skills
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-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-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.
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.
archive-reprocessing
Flexible, version-tracked reprocessing system for archive transformations using design patterns (Strategy, Template Method, Observer). Activate when working with tools/scripts/lib/, reprocessing scripts, transform versions, archive transformations, metadata transformers, or incremental processing workflows.
archive-workflow
Archives completed FABER workflow state and artifacts to cloud storage for historical tracking and analysis
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
obsidian-daily
Manage Obsidian Daily Notes via obsidian-cli. Create and open daily notes, append entries (journals, logs, tasks, links), read past notes by date, and search vault content. Handles relative dates like "yesterday", "last Friday", "3 days ago".
obsidian-additions
Create supplementary materials attached to existing notes: experiments, meetings, reports, logs, conspectuses, practice sessions, annotations, AI outputs, links collections. Two-step process: (1) create aggregator space, (2) create concrete addition in base/additions/. INVOKE when user wants to attach any supplementary material to an existing note. Triggers: "addition", "create addition", "experiment", "meeting notes", "report", "conspectus", "log", "practice", "annotations", "links", "link collection", "аддишн", "конспект", "встреча", "отчёт", "эксперимент", "практика", "аннотации", "ссылки", "добавь к заметке".
observe
Query and manage Observe using the Observe CLI. Use when the user wants to run OPAL queries, list datasets, manage objects, or interact with their Observe tenant from the command line.