plan:archive

To archive completed development plans, this skill moves project files like plan.md and execution-log.md into a timestamped directory and cleans up associated session metadata. It requires filesystem access to perform directory operations and validate session state.

The best way to remove stale session references is using an automated session cleanup process that identifies and deletes process-specific temporary files. This ensures your active workspace remains clean after completing complex iterative development workflows.

Automated plan archiving works by moving plan files, execution logs, and supporting assets into a structured archive folder. This mechanism manages the lifecycle of development documentation and prevents clutter from tracking multiple iterative plans.

Yes, you need filesystem access to move plan.md files to an archive directory. The archiving process performs directory operations and relies on process monitoring to validate session state before cleaning up associated metadata.

You should archive development plans when a task is completed or abandoned to properly store the work and clean up session state. Archiving after finishing a complex task keeps your active workspace uncluttered for future iterations.