Skill

archive

Archive a completed plan to .devloop/archive/

npx claudepluginhub zate/cc-plugins --plugin devloop

Tool Access

This skill is limited to using the following tools:

ReadBashBash(${CLAUDE_PLUGIN_ROOT}/scripts/*.sh:*)AskUserQuestion

Preview

Archive a completed plan to `.devloop/archive/` and clear the active plan. **You do the work directly.**

SKILL.md

Similar Skills

tidy

Analyzes docs/arc/plans/ for completed plans by checking file existence and git history, then archives or deletes them one at a time with confirmation. Use after implementation to tidy stale docs.

arc

Planning with Files

Sets up persistent 3-file markdown workflow (task_plan.md, findings.md, progress.md) for planning phases, tracking progress, and logging findings across AI coding sessions.

aradotso-trending-skills-37

execute-plan

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.

1 file

amplify

Stats

Parent Repo Stars6

Parent Repo Forks1

Last CommitApr 5, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Archive - Move Completed Plan to Archive

Archive a completed plan to .devloop/archive/ and clear the active plan. You do the work directly.

Step 1: Check Plan Status

"${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"

Step 2: Show What Will Be Archived

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

Step 3: Confirm or Auto-Archive

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"

Step 4: Execute Archive

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.

Step 5: Report Result

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]

Quick Reference

Scenario	Action
Plan complete	Archive directly
Plan incomplete	Ask before force-archive
No plan	Show error message
--force argument	Skip confirmation