tidy

Archive or delete completed plans in docs/plans with user confirmation.

26|2|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/howells/arc --skill tidy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tidy
Source: https://github.com/howells/arc/tree/main/skills/tidy
Command: npx skills add https://github.com/howells/arc --skill tidy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tidies planning documents by archiving or deleting completed plans in docs/plans/. This reduces clutter from planning work and ensures only active plans remain accessible.

Core Features & Use Cases

  • One-at-a-time archival/deletion of completed plans
  • Status checks based on implemented files and commits
  • Archive default location: docs/plans/archive/
  • Works with optional assets in docs/plans/assets

Quick Start

Trigger the tidy workflow to clean up docs/plans by archiving or deleting completed plans one at a time.

Frequently Asked Questions about tidy

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

FAQPage Schema
How do I archive completed planning docs automatically?

You can archive completed planning docs by running the tidy workflow, which detects implemented plans in the docs/plans folder and moves them to docs/plans/archive/ one at a time with explicit user confirmation.

How does a tool know which planning documents to delete or archive?

To determine which planning documents to archive or delete, the tool checks file existence for implemented features and optionally analyzes git commit history signals to verify completion status.

Can I keep planning assets when archiving completed plans?

Yes, you can keep planning assets when archiving completed plans because the workflow respects files stored in the docs/plans/assets directory and processes them alongside the main planning documents.

What is the best way to clean up old planning documents in my repository?

The best way to clean up old planning documents is using a one-at-a-time archival process that moves completed plans to an archive folder, ensuring only active plans remain accessible while reducing folder clutter.

Do I need git history to tidy up planning folders?

No, you do not need git history to tidy up planning folders because the tool relies primarily on file existence to detect implemented plans, using optional git history signals only as a secondary confirmation.

Planning document cleanup not working for batch operations?

Planning document cleanup processes strictly one file at a time and requires explicit user confirmation for each action, so batch operations are not supported and each completed plan must be approved individually.