persist

Copy approved plan files to a timestamped filename in the plans directory.

12|2|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/hartphoenix/weft --skill persist-hartphoenix
Or copy as Structured Prompt for Agentā–¼
Please help me install this Agent Skill.
Skill: persist
Source: https://github.com/hartphoenix/weft/tree/main/.claude/skills/persist
Command: npx skills add https://github.com/hartphoenix/weft --skill persist-hartphoenix

SYSTEM DOCUMENTATION & REQUIREMENTS

šŸ’” This Skill includes scripts (resource) components.

What problem does it solve?

This Skill simplifies the process of saving current planning files by automating file copying and organization, reducing manual effort and errors.

Core Features & Use Cases

  • Plan Saving: Copies the latest plan file from the internal plans directory to a structured location with a descriptive name.
  • Automation: Ensures the plan is stored systematically for easy retrieval and review.
  • Use Case: After approving a project plan, use this Skill to save the finalized version with a date-based filename for documentation and future reference.

Quick Start

Use the persist skill to save your current plan by copying the most recent plan file into the plans directory with a timestamped filename.

Frequently Asked Questions about persist

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

FAQPage Schema
How do I automate saving and organizing project plan files?ā–¼

To automate saving project plan files, you need a tool that handles file copying, naming, and directory creation. This ensures your finalized plans are stored systematically with descriptive, date-based filenames for easy retrieval.

What is the best way to keep approved project plans organized for documentation?ā–¼

The best way to keep approved project plans organized is to save them into a structured directory with timestamped filenames. This approach ensures consistency across your documentation and simplifies future retrieval and review.

How does automated file organization work for project planning workflows?ā–¼

Automated file organization for project planning works by copying the latest plan file from an internal directory to a dedicated location. It automatically generates a descriptive, date-based name to ensure the plan is stored systematically.

Do I need specific file system permissions to automate copying and saving plan files?ā–¼

Yes, you need file system access and standard file operation permissions to automate copying and saving plan files. The automation requires these permissions to correctly handle directory creation and file copying workflows.

Can I use this automation for pre-serialization plan saving?ā–¼

Yes, you can use this automation for pre-serialization plan saving. It handles file copying and organization based on plan approval or pre-serialization states, ensuring your project management files remain consistent and easily accessible.

Why should I use a single command to save and organize project plans?ā–¼

Using a single command to save and organize project plans reduces manual effort and minimizes human error. It systematically copies your current planning file into a structured location with a descriptive name for reliable documentation.