docs-archiver

Archive completed Workstream tasks to docs/archive after verifying report.md.

1|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/kellyson520/TG-ONE --skill docs-archiver
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-archiver
Source: https://github.com/kellyson520/TG-ONE/tree/main/.agent/skills/docs-archiver
Command: npx skills add https://github.com/kellyson520/TG-ONE --skill docs-archiver

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Keeps the Active Workspace clean by moving completed tasks from docs/Workstream_* to docs/archive/ without deleting data, ensuring historical records remain intact.

Core Features & Use Cases

  • Automated discovery of completed tasks in docs/Workstream_* directories.
  • Safe archiving to docs/archive/{Workstream}/{TaskName} only after confirming completion via report.md (and optional todo.md status checks).
  • Post-archive maintenance to refresh the docs tree (docs-maintenance).

Quick Start

Run python .agent/skills/docs-archiver/scripts/archive_tasks.py to archive eligible completed tasks.

Frequently Asked Questions about docs-archiver

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

FAQPage Schema
How do I automate archiving completed documentation tasks in Workstreams?

You can automate archiving completed Workstream tasks by running the archive_tasks.py script, which moves finished tasks from docs/Workstream_* directories to docs/archive/{Workstream}/{TaskName} and creates the destination path if needed.

What conditions must a Workstream task meet before it can be safely archived?

A Workstream task can be safely archived only when a report.md file exists in the task directory, and if a todo.md is present, all its items must be checked off with no unchecked items remaining. This ensures data is not lost.

Does archiving Workstream tasks delete the original documentation files?

Archiving Workstream tasks does not delete documentation files. It moves completed tasks from active Workstream directories to docs/archive/ to maintain workspace hygiene while keeping historical records fully intact.

What happens to the documentation tree after moving completed tasks to the archive?

After moving completed tasks to the archive, a post-archive maintenance pass is required to refresh and update the docs tree, ensuring the active workspace structure accurately reflects the remaining unarchived tasks.

When should I avoid automatic task archiving in my documentation workflow?

Avoid automatic task archiving if a task lacks a final report.md file or still has unchecked items in todo.md, as the safety mechanism prevents moving incomplete documentation away from the active Workstream directory.