merge-archive-plan

Archive completed implementation plans with metadata after PR merges.

1|Updated Dec 21, 2025

Search Tags:#project organization #archiving #plan management

Ready to run

npx skills add https://github.com/dopsonbr/agent-kit --skill merge-archive-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: merge-archive-plan
Source: https://github.com/dopsonbr/agent-kit/tree/main/content/skills/merge-archive-plan
Command: npx skills add https://github.com/dopsonbr/agent-kit --skill merge-archive-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill maintains a clean project structure by moving completed implementation plans to an archive directory with comprehensive metadata.

Core Features & Use Cases

Plan Archiving: Moves completed plans to docs/plans/archive/ with execution history, lessons learned, and rollback information preserved for future reference.

Quick Start

After the PR for plan 0042_user-auth is merged, invoke /ak-merge-archive-plan to move the plan to the archive with full metadata.

Frequently Asked Questions about merge-archive-plan

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

FAQPage Schema

How do I archive completed implementation plans after merging to main?▼

Archive completed plans by invoking the merge-archive-plan Skill after your plan's PR merges to main. The Skill moves the plan file to docs/plans/archive/, prepends archive metadata including execution history and lessons learned, and commits the change with a standardized archive message.

What metadata is preserved when archiving a plan?▼

Plan archiving preserves PR metadata, commit information, execution history, lessons learned, and rollback information. This metadata is enriched in an archive header template and stored alongside the plan in docs/plans/archive/ for future reference.

When should I archive implementation plans?▼

Archive plans after their implementation PR merges to main or when plan-execute completes on main. Archiving maintains a clean project structure by moving completed plans out of the active planning directory while retaining full historical context.

Does archiving use git to move plan files?▼

Yes, archiving uses git mv to relocate plan files to docs/plans/archive/, preserving git history. This ensures the move is tracked in version control and committed with the standardized archive message.

Can I archive plans from branches other than main?▼

The Skill archives plans when they merge to main or plan-execute completes on main. It is designed for post-merge archiving workflows, so plans should be moved only after reaching the main branch.