Stats
Actions
Tags
From devloop
Archives completed devloop plans from .devloop/plan.md to .devloop/archive/, clears active plan, checks completion status, and confirms for incomplete plans or --force use.
How this skill is triggered — by the user, by Claude, or both
Slash command
/devloop:archiveThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Archive a completed plan to `.devloop/archive/` and clear the active plan. **You do the work directly.**
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:plan to create a new plan.
If plan has pending tasks: Show status and ask:
AskUserQuestion:
questions:
- question: "Plan has N pending tasks. Archive anyway?"
header: "Incomplete"
multiSelect: false
options:
- label: "Archive anyway"
description: "Force archive incomplete plan"
- label: "Continue work"
description: "Keep working on pending tasks"
- label: "Cancel"
description: "Don't archive"
Use the Read tool with limit: 20 on .devloop/plan.md to show the plan header.
Display:
Plan to archive:
Title: [Plan title]
Tasks: N completed / M total
Created: [date]
Archive destination: .devloop/archive/YYYY-MM-DD-{slug}.md
If plan is complete: Skip confirmation — execute archive directly.
If plan is incomplete (user chose "Archive anyway" in Step 1): Execute archive with --force.
If --force argument: Skip confirmation — execute archive directly.
Otherwise: Ask:
AskUserQuestion:
questions:
- question: "Archive this plan?"
header: "Confirm"
multiSelect: false
options:
- label: "Archive now"
description: "Move plan to archive, clear active plan"
- label: "Cancel"
description: "Keep plan active"
If confirmed (or auto-archiving complete plan, or --force):
"${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:plan --deep "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 |
npx claudepluginhub zate/cc-plugins --plugin devloopArchives a completed or abandoned plan by moving it to an archived folder with metadata and timestamp.
Executes tasks from PLAN.md sequentially with human oversight, handling task splitting, clarifying questions, tests, and learning persistence. Useful for deliberate progress on planned work.
Organizes complex tasks using a Manus-style planning system. Creates task_plan.md, findings.md, and progress.md files for project planning, multi-step plans, and session recovery after /clear.