Archive a completed plan to .devloop/archive/
Moves completed plans to archive directory and clears active plan.
/plugin marketplace add Zate/cc-plugins/plugin install zate-devloop-plugins-devloop@Zate/cc-plugins[--force]Archive a completed plan to .devloop/archive/ and clear the active plan. You do the work directly.
"${CLAUDE_PLUGIN_ROOT}/scripts/check-plan-complete.sh" .devloop/plan.md
Parse the JSON output to get task counts.
If no plan exists:
No active plan to archive.
Run /devloop or /devloop:spike to create a new plan.
If plan has pending tasks: Show status and ask:
AskUserQuestion:
question: "Plan has N pending tasks. Archive anyway?"
header: "Incomplete"
options:
- label: "Archive anyway"
description: "Force archive incomplete plan"
- label: "Continue work"
description: "Keep working on pending tasks"
- label: "Cancel"
description: "Don't archive"
Read the plan header to show the user:
head -20 .devloop/plan.md
Display:
Plan to archive:
Title: [Plan title]
Tasks: N completed / M total
Created: [date]
Archive destination: .devloop/archive/YYYY-MM-DD-{slug}.md
AskUserQuestion:
question: "Archive this completed plan?"
header: "Confirm"
options:
- label: "Archive now"
description: "Move plan to archive, clear active plan"
- label: "Cancel"
description: "Keep plan active"
If confirmed (or --force in arguments):
"${CLAUDE_PLUGIN_ROOT}/scripts/archive-plan.sh" .devloop/plan.md
If user selected "Archive anyway" for incomplete plan:
"${CLAUDE_PLUGIN_ROOT}/scripts/archive-plan.sh" .devloop/plan.md --force
Parse the JSON output.
On success:
Plan archived successfully!
Archived to: .devloop/archive/YYYY-MM-DD-{slug}.md
Tasks completed: N
Next steps:
- /devloop:spike "topic" - Start new exploration
- /devloop - Start new plan directly
- git add .devloop/archive/ - Commit archive to git
On failure:
Archive failed: [error message]
| Scenario | Action |
|---|---|
| Plan complete | Archive directly |
| Plan incomplete | Ask before force-archive |
| No plan | Show error message |
| --force argument | Skip confirmation |