Archive Completed Plans

Consolidate unreferenced completed plans into monthly archive summaries.

1|Updated Oct 6, 2024
One-click install
npx skills add https://github.com/TairuFramework/enkaku --skill archive-completed-plans
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Archive Completed Plans
Source: https://github.com/TairuFramework/enkaku/tree/main/.claude/skills/archive
Command: npx skills add https://github.com/TairuFramework/enkaku --skill archive-completed-plans

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintain an organized project by archiving completed plans that are no longer actively referenced, reducing clutter and improving discoverability of current work.

Core Features & Use Cases

  • Automated Archiving: Consolidates completed plans into monthly summaries.
  • Reference Checking: Identifies plans that are still linked from active or future work.
  • Stale Reference Fixing: Updates or removes links to archived plans.
  • Use Case: Regularly run this skill to keep your completed plans tidy and ensure that references to them are managed appropriately, preventing broken links and making it easier to focus on ongoing tasks.

Quick Start

Invoke the Archive Completed Plans skill to consolidate unreferenced completed plans into monthly summaries.

Frequently Asked Questions about Archive Completed Plans

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

FAQPage Schema
How do I archive completed plans and reduce project clutter?

Updating stale references before archiving completed plans prevents broken links. The system scans active, next, and backlog directories to identify linked plans, then updates or removes stale cross-references before generating monthly summaries.

What happens if I archive completed plans that are still referenced in active work?

Archiving referenced plans triggers a stale reference check. The skill scans active, next, and backlog directories for cross-references, automatically updating or removing links to prevent broken paths before consolidating the completed plans.

Do I need any specific dependencies to consolidate completed plans into monthly summaries?

No dependencies are required to consolidate completed plans into monthly summaries. The skill operates independently to scan project directories, check cross-references, generate archive summaries, and commit changes directly to your repository.

When should I run a completed plans cleanup in my project?

Run a completed plans cleanup regularly to maintain project organization and discoverability of current work. This prevents the accumulation of unreferenced completed plans and ensures stale cross-references are managed before broken links disrupt ongoing tasks.