ai-memory-consolidate-reduce

Consolidates completed plan files in .ai-memory/plans/ into compact milestone summaries with git backup.

Updated May 16, 2026
One-click install
npx skills add https://github.com/alimtvnetwork/img-pdf-v2 --skill ai-memory-consolidate-reduce-alimtvnetwork
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ai-memory-consolidate-reduce
Source: https://github.com/alimtvnetwork/img-pdf-v2/tree/main/.agents/skills/ai-memory-consolidate-reduce
Command: npx skills add https://github.com/alimtvnetwork/img-pdf-v2 --skill ai-memory-consolidate-reduce-alimtvnetwork

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Over time, the .ai-memory/plans/ directory accumulates dozens of completed plan files and subtasks, making navigation slow and bloating context. This Skill clusters, merges, and re-sequences those files into minimal milestone summaries while preserving all verified outcomes. ## Core Features & Use Cases - Safety Backup First: Creates a timestamped git backup branch and pushes it to origin before any modification or deletion. - Aggressive Clustering: Combines 2, 3, or more related tasks into single milestone files and prunes guideline-only micro-plans with no business logic. - Monotonic Re-sequencing: Renumbers completed plans continuously (01-, 02-, 03-) with lowercase filenames and zero gaps, then syncs the index files. - Use Case: After finishing a large feature with 40 completed plan files, run this Skill to compact them into a handful of milestone summaries while keeping error contracts and decision logs intact. ## Quick Start Ask the AI to consolidate and re-sequence all completed plans in .ai-memory/plans/ with a safety backup branch.

Frequently Asked Questions about ai-memory-consolidate-reduce

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

FAQPage Schema
How do I reduce the number of completed plan files in .ai-memory/plans/?

Run the consolidation workflow, which clusters 2 or more related tasks into single milestone files, prunes guideline-only micro-plans, and re-sequences the completed directory with continuous numbering.

How to safely merge completed plans without losing data?

The Skill creates a timestamped git backup branch and pushes it to origin before modifying anything. All core architectural concepts, verified outcomes, error contracts, and decision logs are preserved during compaction.

Does plan consolidation delete any completed task information?

It removes only pure formatting or routine guideline-fix micro-plans containing zero business logic. Repeated checklists are replaced with a pointer to .ai-memory/coding-guidelines.md rather than duplicated.

What happens to plan file numbering after consolidation?

Files in .ai-memory/plans/completed/ are re-sequenced monotonically as 01-, 02-, 03- with lowercase filenames and no gaps. The index files 01-index.md and what-to-read.md are updated to match.

When should I not run plan consolidation?

Avoid running it on active or in-progress plans, since the workflow targets only completed files. Also ensure your git remote is reachable, because the mandatory backup push must succeed before changes begin.