s:archive

Archive completed tasks into a timestamped directory and update git logs.

Updated Jan 22, 2026
One-click install
npx skills add https://github.com/Hoang604/get-thing-done --skill s-archive
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: s:archive
Source: https://github.com/Hoang604/get-thing-done/tree/main/.claude/skills/s-archive
Command: npx skills add https://github.com/Hoang604/get-thing-done --skill s-archive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed task work into a timestamped archive to preserve history.

Core Features & Use Cases

  • Move completed task folders into a time-stamped archive directory.
  • Update task state in BACKLOG.md and JOURNAL.md to reflect completion.
  • Preserve related files (SPEC.md, ROADMAP.md, and phase documents) within the archive for future reference.
  • Enable easy auditing and rollback by retaining historical records.

Quick Start

Run the archive command for the finished task to move it into the archive directory and update the backlog and journal.

Frequently Asked Questions about s:archive

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

FAQPage Schema
How do I archive completed GTD tasks while preserving backlog and journal history?

To archive completed GTD tasks, this Skill moves finished task folders into a timestamped archive directory while updating BACKLOG.md and JOURNAL.md to reflect completion status. It preserves SPEC.md, ROADMAP.md, and phase folders within the archive for future reference and auditing.

What is the best way to move completed task folders out of an active workflow without losing project history?

The best way to move completed task folders is archiving them into a timestamped directory that retains SPEC.md, ROADMAP.md, and phase documents. This approach preserves project history and enables easy rollback while keeping the active workspace clean.

Does archiving completed tasks automatically update the backlog and journal entries?

Yes, archiving completed tasks automatically updates both BACKLOG.md and JOURNAL.md to reflect the completion state. The Skill ensures automated state updates across your GTD workflow files during the archive process.

Can I trace archived task work through git commit logs?

Yes, you can trace archived task work through git commit logging. The Skill creates a git commit during the archiving process, ensuring full traceability and historical record of when tasks were moved and their states updated.

Do I need a specific folder structure to archive tasks under the .gtd directory?

Yes, this Skill applies to GTD-style workflows where tasks live under a .gtd directory and require backlog updates, journal entries, and archiving of SPEC.md, ROADMAP.md, and phase folders. Your project must follow this structure for the archiving automation to work correctly.

When should I not use automated task archiving in my workflow?

You should avoid automated task archiving if your project does not follow a GTD-style workflow with .gtd directory structures, BACKLOG.md, and JOURNAL.md files. The Skill depends on these specific files and folder conventions to function properly.