.claude/skills/s-archive/SKILL.md
Archive completed task/spec work to ./.gtd/archive/
npx skillsauth add Hoang604/get-thing-done s:archiveInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Core responsibilities:
Flow: Verify Exists → Update Backlog → Log Journal → 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 archiveDestination:
./.gtd/archive/<task_name>-{timestamp}/ — Archived task workUpdates:
./.gtd/BACKLOG.md — Mark item as [x] complete./.gtd/JOURNAL.md — Append completion eventFiles to archive:
Only archive when task is complete or abandoned.
Keep all files for future reference and learning.
Backlog and Journal must reflect the completion.
After archiving, task folder is removed to keep .gtd/ clean.
</philosophy> <process>If no argument provided, ask user:
Which task would you like to archive?
Available tasks:
- {task 1}
- {task 2}
Verify ./.gtd/<task_name>/ exists:
if [ ! -d "./.gtd/<task_name>" ]; then
echo "Error: Task '<task_name>' not found"
exit 1
fi
If ./.gtd/BACKLOG.md exists:
- [ ] **{task_name}**)[ ] to [x]Example:
Before: - [ ] **audio-gateway** — Opus decoding, VAD
After: - [x] **audio-gateway** — Opus decoding, VAD
If ./.gtd/JOURNAL.md exists:
Append a new row to the journal table:
| {date} | Task completed: {task_name} | Complete | {task_name} |
Generate archive name with timestamp:
TIMESTAMP=$(date +%Y%m%d-%H%M%S)
ARCHIVE_DIR="./.gtd/archive/<task_name>-${TIMESTAMP}"
mkdir -p "./.gtd/archive"
Move entire task folder to archive:
mv "./.gtd/<task_name>" "${ARCHIVE_DIR}"
Commit the archive and state updates:
git add ./.gtd/archive/ ./.gtd/BACKLOG.md ./.gtd/JOURNAL.md
git commit -m "chore: archive task <task_name> to {task_name}-${TIMESTAMP}"
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
GTD ► TASK ARCHIVED ✓
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Task: {task_name}
Archived to: ./.gtd/archive/{task_name}-{timestamp}/
Phases archived: {count}
Files archived: {count}
✓ BACKLOG.md updated
✓ JOURNAL.md updated
✓ Task folder removed from ./.gtd/
─────────────────────────────────────────────────────
<forced_stop> STOP. The workflow is complete. Do NOT automatically run the next command. Wait for the user. </forced_stop>
testing
manual trigger by user, do not auto invoke
tools
manual trigger by user, do not auto invoke
development
Trace execution paths and document how code actually behaves. Use when you need to understand how features work, walk through code flows, explain component behavior, trace where data comes from, understand relationships between components, or audit for orphaned events and dead code.
testing
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.