Clean up completed plans in docs/plans/. Archives or deletes finished plans. Use when asked to "clean up plans", "tidy the docs", "archive old plans", or after completing implementation to remove stale planning documents.
Archives or deletes completed implementation plans from the docs/plans/ folder after confirming each action.
/plugin marketplace add howells/arc/plugin install arc@howellsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Clean up the docs/plans/ folder by analyzing which plans have been implemented. Archive what's done, keep what matters.
--quick): Only show implemented plans ready to archiveUse Glob tool: docs/plans/*.md
Handle empty states:
docs/plans/: "No plans folder found. Nothing to tidy!"Preview:
Let me tidy up your plans folder...
Found [N] plans in docs/plans/
For each plan file:
1. Parse metadata from filename:
YYYY-MM-DD prefix-design.md or -implementation.md suffix2. Extract signals from plan content:
3. Check implementation status:
Use Glob tool: Check if planned files exist (use paths from plan)
Use Bash for git history:
git log --after="YYYY-MM-DD" --oneline -- [file-paths]
Use Grep tool: Pattern identifier in [file-paths] — check for key identifiers
4. Determine status:
| Condition | Status |
|---|---|
| 70%+ signals positive | Implemented |
| 30-70% signals positive | Partial |
| 0 signals positive | Outstanding |
| Cannot parse/analyze | Unknown |
## Plan: [Topic] ([YYYY-MM-DD])
[1-3 sentence summary from plan]
**Status:** [status]
**Evidence:**
- [file] exists (planned to create)
- [file] modified after plan date
- [N] commits after plan date
- OR: No activity found on planned files
---
What should I do?
1. Archive (move to docs/plans/archive/)
2. Delete (remove file and assets)
3. Keep (leave in place)
4. Skip (decide later)
Wait for user response before proceeding to next plan.
Archive:
mkdir -p docs/plans/archive/
mv docs/plans/[plan].md docs/plans/archive/
# Move associated assets if they exist
mv docs/plans/assets/[topic]/ docs/plans/archive/assets/ 2>/dev/null
Delete:
rm docs/plans/[plan].md
rm -rf docs/plans/assets/[topic]/ 2>/dev/null
Keep/Skip: No action, continue to next plan.
After all plans processed:
## Tidy Complete!
| Action | Count |
|--------|-------|
| Archived | X |
| Deleted | Y |
| Kept | Z |
| Skipped | W |
Your plans folder is now tidy!
Offer to commit:
Want me to commit these changes?
If yes:
git add docs/plans/
git commit -m "docs: tidy up completed plans"
Paired design + implementation:
Plans with assets:
docs/plans/assets/YYYY-MM-DD-topic/Very old plans (>60 days, no activity):
Unparseable plans:
Friendly, unobtrusive:
NOT: overly cute, emoji-heavy, or verbose.
docs/plans/Activates when the user asks about AI prompts, needs prompt templates, wants to search for prompts, or mentions prompts.chat. Use for discovering, retrieving, and improving prompts.
Search, retrieve, and install Agent Skills from the prompts.chat registry using MCP tools. Use when the user asks to find skills, browse skill catalogs, install a skill for Claude, or extend Claude's capabilities with reusable AI agent components.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.