home / skills / abdullahbeam / nexus-design-abdullah / archive-project

This skill archives completed projects by moving them to 05-archived and updating project maps, keeping your active list focused.

npx playbooks add skill abdullahbeam/nexus-design-abdullah --skill archive-project

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
2.4 KB
---
name: archive-project
description: Load when user says "archive project", "archive [project-name]", "move to archived". Moves completed projects to 05-archived/ folder for clean project list.
---

# Archive Project

Move completed projects to archive for a clean, focused project list.

## Purpose

Archive projects that are:
- 100% complete
- Cancelled or on-hold
- No longer active

Archived projects stay accessible but don't clutter your active list.

---

## Workflow

### Step 1: Initialize TodoList

Create TodoWrite with all workflow steps:
```
- [ ] Identify project to archive
- [ ] Load and verify project status
- [ ] Confirm archive action
- [ ] Move project to archive
- [ ] Update project-map.md
- [ ] Display success message
- [ ] Close session to save progress
```

**Mark tasks complete as you finish each step.**

### Step 2: Identify Project

**If user specified project** (e.g., "archive 01-build-nexus-v3") → Use that

**If not** → List active projects and ask: "Which project?"

### Step 3: Load & Verify

Load `02-projects/{ID}-{name}/01-planning/tasks.md` and overview.md

Count checkboxes → Calculate progress

Display:
```
Project: {name}
Progress: X/Y tasks (Z%)
Status: {status}

[If <100%] → "Not complete. Archive anyway? (yes/no)"
[If 100%] → "Ready to archive!"
```

### Step 4: Confirm

Ask: "Archive {name}? This moves it to 05-archived/. (yes/no)"

**If "no"** → Exit

### Step 5: Archive

1. **Create 05-archived/ if needed**
2. **Move project**: `02-projects/{ID}-{name}/ → 05-archived/{ID}-{name}/`
3. **Update project-map.md**:
   - Remove from Active Projects
   - Add to Archived Projects section
   - Clear Current Focus if this was it
4. **Add archive metadata to overview.md**:
   ```yaml
   archived: 2025-11-02
   ```

### Step 6: Confirm Success

```
✅ Archived: {name}
Location: 05-archived/{ID}-{name}/
Final progress: X/Y (Z%)

View archived: Say "list archived"
```

### Final Step: Close Session

**Automatically trigger the close-session skill**:
```
Auto-triggering close-session to save progress...
```

This ensures the archive action is saved to memory and project-map.md is properly updated.

---

## Additional Commands

**"list archived"** → Scan 05-archived/ and display all archived projects

**"restore [project]"** → Move project back from 05-archived/ to 02-projects/

---

## Notes

- Archive ≠ Delete (all files preserved)
- Keeps active list focused
- Can restore anytime

---

**Clean list = clear mind!**

Overview

This skill automates archiving completed or inactive projects by moving them into a 05-archived/ folder so your active project list stays focused. It verifies project progress, requests confirmation, updates project-map.md and overview metadata, then closes the session to persist changes. Archive operations preserve all files and support later restoration.

How this skill works

When invoked with commands like "archive project" or "archive [project-name]", the skill locates the project directory under 02-projects/, reads planning tasks and overview to compute progress, and prompts for confirmation if not fully complete. On approval it creates 05-archived/ if needed, moves the project folder, updates project-map.md (Active → Archived, clears current focus if required), appends archived metadata to overview.md, and triggers a close-session action to save state.

When to use it

  • You finished all tasks for a project (100% complete).
  • A project is cancelled, on-hold, or no longer active.
  • You need a cleaner active project list for focus.
  • You want to preserve project files but remove them from daily view.
  • You plan to restore a project later if needed.

Best practices

  • Confirm project identity before archiving when multiple similar names exist.
  • Run progress verification to avoid accidentally archiving incomplete work.
  • Ensure project-map.md is in repository root and writable so updates succeed.
  • Leave a short archive note in overview.md if the project was cancelled or paused.
  • Use the built-in restore command to move archived projects back to active when needed.

Example use cases

  • User says "archive 01-build-nexus-v3" after marking all planning tasks complete.
  • User requests "archive project" and selects a cancelled project from the active list.
  • Automatically move a completed sprint project into 05-archived/ for annual cleanup.
  • Audit shows an old on-hold project; archive to keep active board concise.
  • Restore a previously archived project for further development using "restore [project]".

FAQ

Does archiving delete project files?

No. Archiving moves the project folder to 05-archived/ and preserves all files.

What if the project is not 100% complete?

The skill reports progress and asks for confirmation before archiving incomplete projects.

How does the skill record the archive date?

It appends an archived: YYYY-MM-DD metadata line to the project's overview.md.