plan-archive

Original：🇨🇳 Chinese

Translated

Archive completed plans from plans/active/ to plans/completed/, supplement verification results and completion time. Suitable for calling after implementation is finished.

2installs

Sourceashe-li/agent-skills

Added on2026-03-07

NPX Install

npx skill4agent add ashe-li/agent-skills plan-archive

SKILL.md Content (Chinese)

View Translation Comparison →

/plan-archive — Archive Completed Plans

Move completed plans in

plans/active/

to

plans/completed/

and add verification results.

ECC Resource Awareness: If a usable code-reviewer agent is available, it can assist in verifying the implementation results in the plan.

Step 1: Locate the Plan to Archive

If an argument (filename or path) is passed in, use it directly. Otherwise, list all

.md

files under

plans/active/

:

bash

ls plans/active/*.md 2>/dev/null

If there are multiple files, sort them by mtime and ask the user which one to select. If there is only one, use it directly. If the directory does not exist or is empty, output "No plan to be archived found" and exit.

Step 2: Read Plan Content

Read the target plan file and confirm:

Whether there is a
```
## Phase
```
or
```
## Step
```
section (implementation steps)
Whether there is a
```
## 驗證
```
or
```
## Verification
```
section
Whether there is a
```
## Industry & Standards Reference
```
section

Step 3: Supplement Verification Results

Add the following at the top of the plan file (right after the

---

frontmatter):

markdown

**Status: ✅ Completed (YYYY-MM-DD)**

Then add or update the

## Verification Results

section, fill in:

Number of passed tests (if any)
Actual execution results (compared with "expectations" in the plan)
Implementation status of industry/academic references — compare with the Industry & Standards Reference of the plan to confirm whether each reference has been actually applied
Any deviations or supplementary explanations

Step 4: Move the File

bash

mkdir -p plans/completed
mv plans/active/<filename>.md plans/completed/<filename>.md

After confirming the move is successful, output:

✅ Archived: plans/completed/<filename>.md

Automation (Hook Configuration)

If you want to automatically save the plan to

plans/active/

after each

ExitPlanMode

, you can configure the PostToolUse hook:

1. Create the hook script

~/.claude/hooks/save-plan-on-exit.sh

:

bash

#!/bin/bash
# PostToolUse hook for ExitPlanMode
# Reads JSON from stdin, copies plan file to project's plans/active/

INPUT=$(cat)

# Extract plan_file path from tool response
PLAN_FILE=$(echo "$INPUT" | python3 -c "
import sys, json
try:
    d = json.load(sys.stdin)
    # ExitPlanMode tool_response may contain the plan file path
    resp = d.get('tool_response', d)
    print(resp.get('plan_file', resp.get('planFile', '')))
except Exception:
    print('')
" 2>/dev/null)

if [ -z "$PLAN_FILE" ] || [ ! -f "$PLAN_FILE" ]; then
  exit 0
fi

# Only act if we're inside a git repo with a plans/ directory pattern
if [ ! -f "$(pwd)/.git/HEAD" ] && [ ! -d "$(pwd)/.git" ]; then
  exit 0
fi

DEST_DIR="$(pwd)/plans/active"
mkdir -p "$DEST_DIR"

SLUG=$(basename "$PLAN_FILE")
cp "$PLAN_FILE" "$DEST_DIR/$SLUG"
echo "[plan-archive] Plan saved to plans/active/$SLUG" >&2

bash

chmod +x ~/.claude/hooks/save-plan-on-exit.sh

2. Configure

~/.claude/settings.json

json

{
  "hooks": {
    "PostToolUse": [
      {
        "matcher": "ExitPlanMode",
        "hooks": [
          {
            "type": "command",
            "command": "bash ~/.claude/hooks/save-plan-on-exit.sh"
          }
        ]
      }
    ]
  }
}

3. Rule (for combined use)

Add to the project's

CLAUDE.md

to ensure that Claude actively calls

/plan-archive

after the implementation is completed:

markdown

### Knowledge Precipitation Checklist Before Commit

5. **Archive plan** — If there is a corresponding plan for this work, execute `/plan-archive` after the implementation is completed
   Move `plans/active/<name>.md` to `plans/completed/`, add verification results

Directory Specification

plans/
├── active/       # In progress (automatically saved by Hook / manually created via /plan)
├── completed/    # Implemented and completed (archived via /plan-archive)
└── archived/     # Long-term archived (old plans no longer referenced)

plan-archive

NPX Install

Tags

SKILL.md Content (Chinese)

/plan-archive — Archive Completed Plans

Step 1: Locate the Plan to Archive

Step 2: Read Plan Content

Step 3: Supplement Verification Results

Step 4: Move the File

Automation (Hook Configuration)

1. Create the hook script

2. Configure
`~/.claude/settings.json`

3. Rule (for combined use)

Directory Specification