skills.rest
allemaar
allemaarCOMMUNITY
Explore all skills by this author →
Website𝕏@allemaarGitHub

plan-cleanup

Removes planning artifacts and tech debt left behind after plan execution.

14|1|Updated Jun 14, 2026
Search Tags:#git#cleanup#tech debt#post-execution#planning artifacts#file removal#workspace hygiene
One-click install
npx skills add https://github.com/allemaar/open-skills --skill plan-cleanup-allemaar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-cleanup
Source: https://github.com/allemaar/open-skills/tree/main/skills/plan-cleanup
Command: npx skills add https://github.com/allemaar/open-skills --skill plan-cleanup-allemaar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a plan runs, workspaces accumulate leftover planning documents, scaffolding files, and temporary artifacts that clutter the repository and create tech debt. This Skill identifies and removes those leftovers safely, with explicit confirmation before any deletion. ## Core Features & Use Cases - Artifact Identification: Scans for planning docs (PLAN.md, implementation_plan.md, *-plan.md), execution scaffolding, and incidental tool directories, verifying each candidate is truly a planning leftover. - Confirmed Removal: Presents the full artifact list and removes only user-approved files, using git rm for tracked files and rm for untracked ones. - Verification and Commit: Confirms each deletion, commits tracked removals with a chore message, and ends with a required terminal declaration. - Use Case: After finishing a multi-phase implementation plan, run the cleanup to delete PLAN.md and temporary stub files, then commit the cleaned tree in one pass. ## Quick Start Ask the agent to clean up the planning artifacts left in the workspace after the plan finished executing.

Frequently Asked Questions about plan-cleanup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I remove planning artifacts after executing a plan?▼

Run the cleanup workflow, which scans for planning docs like PLAN.md and *-plan.md files, lists every candidate artifact, and removes them only after your confirmation. Tracked files are removed with git rm and untracked files with rm.

What files count as planning artifacts in a project?▼

Planning artifacts include PLAN.md, implementation_plan.md, root-level *-plan.md files, temporary stub or scaffolding files created for the plan run, and incidental tool directories. Each candidate is verified to confirm it is not needed by the project going forward.

Does plan cleanup delete files without asking?▼

No. The workflow must list every identified artifact and wait for explicit confirmation before removing anything. You can approve all, skip specific files, or cancel entirely, and skipped files are never touched.

Can cleanup remove files outside the current project?▼

No. The rules explicitly prohibit removing files outside the current project scope, and files the user skipped are never deleted. Only artifacts identified in the scan phase are eligible for removal.

What is the difference between plan-cleanup and plan-evolve?▼

plan-cleanup only removes leftover artifacts and tech debt after execution, adding no new work. plan-evolve treats the shipped work as v1 and plans the next iteration, which is a forward-looking planning activity rather than deletion.

Related Skills

Explore More Software Engineering Skills→
ncy08ncy08

implement

Execute approved implementation plans phase by phase with validation checkpoints.

Community
Advanced
fivetakufivetaku
114

git-teacher-upload

Push committed Git work to GitHub with beginner-friendly explanations.

Community
Intermediate
krzemienskikrzemienski
2

honest-reflections

Analyze claimed completion against actual work delivery to reveal gaps.

Community
Advanced
baseballyamabaseballyama
218

repo-hygiene

Audits repository structure, naming, gitignore coverage, and CI configuration for OSS cleanliness.

Community
Advanced