skill-archive-task

Automating task documentation archiving moves your current `TASK.md` file to a dedicated `docs/tasks/` directory with a unique filename. This prevents data loss by saving completed tasks before new ones begin.

Unique task ID generation assigns identifiers and slugs to create filenames like `task-033-login-flow.md`. It manages ID updates within the file to ensure historical traceability and prevent naming conflicts in the archive directory.

Maintaining a clean workspace involves triggering automated file relocation to move completed task files into an archive. This validates successful file transfers and ensures superseded tasks are preserved with unique identifiers.

No dependencies are required to automate task archiving in your documentation workflow. The process runs standalone to manage file relocation, task ID updates, and slug generation without external packages.

Task archiving issues occur when file relocation validation fails or the target `docs/tasks/` directory is inaccessible. The process validates successful file transfers to prevent data loss and maintain historical integrity.

Yes, file management automation prevents data loss when superseding task markdown files by moving them to an archive directory. It ensures historical integrity by validating the relocation and applying unique task IDs.