cleanuplisted

Use when the user asks to clean up a project, remove old plans, tidy docs, cleanup stale files, prune completed specs, or inspect artifacts after shipping a major feature. Inputs - project root, current branch context, and user confirmation before deleting or rewriting files. Do not use when the user wants disk-space cleanup, dependency pruning, code refactoring, or documentation generation; use a system-cleanup, package, refactor, or docs workflow instead. Produces a cleanup report classifying artifacts as remove, update, keep, or review, then confirmed file/doc changes. Escalate if deletion risk is ambiguous, living docs are involved, or more than two docs need substantive updates.
Naoray/skills · ★ 1 · Data & Documents · score 64

Install: claude install-skill Naoray/skills

# Project Cleanup **Evidence tier**: P **Basis**: Practitioner workflow for repository hygiene, stale artifact review, and conservative documentation cleanup. **Source IDs**: cleanup/SKILL.md workflow; git branch and markdown artifact audit conventions **Reviewed**: 2026-05-12 Find stale plans, specs, and documentation artifacts. Remove what's been implemented, update what's drifted, and leave the project tidy. ## Workflow ### Step 1: Discover artifacts Run three discovery passes. If your runtime supports parallel sub-tasks (subagents, parallel tool calls), run them concurrently; otherwise run sequentially. All passes are read-only. **Pass A — Plans & specs.** Return each file's path, title, and status (fully implemented / partially implemented / abandoned / active). Scan locations vary by tooling stack — see [`references/registry-integration.md`](references/registry-integration.md) for the concrete path table per backend. Common targets: project-level `PLAN.md`/`SPEC.md`/`DESIGN.md`/`TODO.md`, any `*.plan.md` or `*.spec.md`, and backend-specific plan dirs. Status rubric: - **Fully implemented**: all checklist items checked, or the described feature exists in code (verify by locating key files/classes the plan names). - **Partially implemented**: some items done, some remaining. - **Abandoned/stale**: no related commits in 30+ days, or references code/branches that no longer exist. - **Active**: modified within 7 days, or references current branch work. **Pass B — Do