From vk
Move completed epics from the active development plan to an archive file to reduce context bloat
How this skill is triggered — by the user, by Claude, or both
Slash command
/vk:archive-epicThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are archiving one or more completed epics from the active development plan. This moves the full epic content to an archive file and replaces it with a one-line summary in the active plan. The goal is to keep `docs/development-plan.md` under ~300 lines of active content.
You are archiving one or more completed epics from the active development plan. This moves the full epic content to an archive file and replaces it with a one-line summary in the active plan. The goal is to keep docs/development-plan.md under ~300 lines of active content.
Read the file docs/development-plan.md to get the current plan contents. If the file doesn't exist, inform the user and suggest running /vk:create-plan first.
Default behavior: If the user didn't specify which epic(s), archive all completed epics automatically. List the epics being archived for confirmation, then proceed.
## Archiving all completed epics
| Epic | Tasks | Action |
|------|-------|--------|
| 1. Foundation | 7 | Archive |
| 2. Core Features | 8 | Archive |
| 3. Supporting | — | Skip (in progress) |
If the user specified specific epic(s), archive only those.
Rules:
Before archiving, confirm:
(COMPLETE)Done statusDepends On references to tasks in this epic that are still in progressIf dependencies exist on the epic's tasks from active epics, warn the user but allow archiving (the dependency info will remain in the active epic's task table).
Archive files live in docs/archive/. Use a descriptive filename:
docs/archive/epics-1-3.md (batch archive)
docs/archive/epic-1-foundation.md (single epic)
If the user is archiving multiple epics, group them into one file.
Archive file format:
# Archived Epics
> Archived from `docs/development-plan.md` on [date]
> These epics are complete and moved here to reduce active plan size.
> Full git history is preserved for all changes.
---
[Full epic content copied verbatim from development-plan.md, including:]
- Epic header
- Description
- Acceptance criteria
- Tasks table
- Task details
- All checkboxes in their current state
If appending to an existing archive file, add the new epic(s) at the end with a separator.
In docs/development-plan.md:
Remove the full epic section (everything from ## Epic N: to the next --- separator)
Add a summary line in a "Completed Epics (archived)" section placed after the Completion Status Summary table and before the first active epic:
## Completed Epics (archived)
| Epic | Tasks | Completed | Archive |
|------|-------|-----------|---------|
| 1. Foundation | 7 tasks | 2026-02-15 | [archive](archive/epics-1-3.md) |
| 2. Core Features | 8 tasks | 2026-03-01 | [archive](archive/epics-1-3.md) |
If the section already exists, append to the table.
Remove the epic from the Completion Status Summary table — archived epics are tracked in the "Completed Epics (archived)" section instead; the summary table only shows active (non-archived) epics.
Add changelog entry in docs/development-plan-changelog.md (prepend at the top of the list):
- **[date]**: Archived Epic N: [Name] to docs/archive/[filename] — [task count] tasks, plan reduced by ~[line count] lines
## Archive Complete
**Archived:** Epic 1: Foundation (7 tasks), Epic 2: Core Features (8 tasks)
**Archive file:** docs/archive/epics-1-2.md
**Lines removed from active plan:** ~180
**Active plan size:** ~250 lines (was ~430)
### What's preserved
- Full epic content in archive file
- Summary row in "Completed Epics (archived)" section
- Git history for all changes
### Next steps
- Commit the changes
- Active epics remain in `docs/development-plan.md` as before
- To review archived epics, read `docs/archive/epics-1-2.md`
If an active task has Depends On: 1.3 and Epic 1 is being archived:
If docs/archive/ already has files:
If every epic is complete, archive them all. The "Completed Epics (archived)" section provides sufficient context in the active plan. The Completion Status Summary table will be empty — that's fine.
/vk:close-epic firstnpx claudepluginhub materemias/claude-vibekanban-plugin --plugin vkGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.