Back to Skills

tidy

verified

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.

View on GitHub

Marketplace

howells-arc

howells/arc

Plugin

arc

Repository

howells/arc
8stars

skills/tidy/SKILL.md

Last Verified

January 25, 2026

Install Skill

Select agents to install to:

Scope:
npx add-skill https://github.com/howells/arc/blob/main/skills/tidy/SKILL.md -a claude-code --skill tidy

Installation paths:

Claude
.claude/skills/tidy/
Powered by add-skill CLI

Instructions

# Tidy Workflow

Clean up the docs/plans/ folder by analyzing which plans have been implemented. Archive what's done, keep what matters.

## Modes

1. **Full mode** (default): Review all plans
2. **Quick mode** (`--quick`): Only show implemented plans ready to archive

## Process

### Step 1: Discover Plans

**Use Glob tool:** `docs/plans/*.md`

**Handle empty states:**
- No `docs/plans/`: "No plans folder found. Nothing to tidy!"
- Empty folder: "Your plans folder is already spotless!"

**Preview:**
```
Let me tidy up your plans folder...

Found [N] plans in docs/plans/
```

### Step 2: Analyze Each Plan

For each plan file:

**1. Parse metadata from filename:**
- Date: `YYYY-MM-DD` prefix
- Topic: middle slug
- Type: `-design.md` or `-implementation.md` suffix

**2. Extract signals from plan content:**
- File paths in "Create:", "File:", "Modify:" sections
- Function/component/type names mentioned
- Test file paths

**3. Check implementation status:**

**Use Glob tool:** Check if planned files exist (use paths from plan)

**Use Bash for git history:**
```bash
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 |

### Step 3: Present to User (One at a Time)

```markdown
## 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.

### Step 4: Execute Actions

**Archive:**

Validation Details

Front Matter
Required Fields
Valid Name Format
Valid Description
Has Sections
Allowed Tools
Instruction Length:
3668 chars