archive-tasks

Compacts completed task files into milestone summaries and moves them to the archive.

6|Updated May 18, 2026
One-click install
npx skills add https://github.com/mokhtarabadi/cognitive-lead-hq --skill archive-tasks-mokhtarabadi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: archive-tasks
Source: https://github.com/mokhtarabadi/cognitive-lead-hq/tree/main/skill-templates/archive-tasks
Command: npx skills add https://github.com/mokhtarabadi/cognitive-lead-hq --skill archive-tasks-mokhtarabadi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Over time, the tasks/completed/ directory accumulates hundreds of finished task files, making project history hard to navigate and bloating the working context. This Skill compacts completed tasks into dense, single-file milestone summaries and archives the originals. ## Core Features & Use Cases - Milestone Summarization: Scans all completed task files and generates a structured summary at docs/history/milestone-X-summary.md, including source distribution, architectural changes, files modified, and acceptance criteria status. - Automated Archiving: Moves completed task files from tasks/completed/ to tasks/archive/ using git mv, staging the new summary and moved files for commit. - Memory Bank Audit: After compaction, audits the project memory bank via list_namespaces and search_memory to detect stale, superseded, or duplicate memory entries, producing a Stale Memory Report that requires Manager approval before any deletion. - Use Case: At the end of a development milestone, run this Skill to condense 25 completed task files into one milestone summary document, archive the originals, and flag outdated memory entries for review. ## Quick Start Run the archive-tasks skill to compact all completed tasks in tasks/completed/ into a new milestone summary and move them to the archive.

Frequently Asked Questions about archive-tasks

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

FAQPage Schema
How do I archive completed tasks in a milestone-based project?▼

Run the archive-tasks skill, which scans tasks/completed/, generates a milestone summary in docs/history/, and moves the completed files to tasks/archive/ using git mv. It also stages the new summary and archived files for commit.

When should I run task compaction and archiving?▼

Run it at the end of each milestone or whenever tasks/completed/ contains more than 20 files. The milestone number is determined by reading the highest existing milestone in docs/history/ and incrementing by one.

What does the milestone summary file contain?▼

The summary at docs/history/milestone-X-summary.md includes the date, task count, source distribution table, architectural changes, files modified, acceptance criteria status, and condensed individual task summaries with type, source, and reasoning.

Does the skill delete memory entries automatically?▼

No. The skill audits memory namespaces and produces a Stale Memory Report listing flagged entries with namespace, key, and reason, but it waits for explicit Manager approval before calling delete_memory on any entry.

What happens if completed task files are not tracked by git?▼

If the files are untracked, use standard mv instead of git mv to move them into tasks/archive/, then run git add tasks/archive/ to stage them before committing.