archive

Move completed AIDLC workflows to a completed directory with archival metadata.

2|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/mikev10/olympus --skill archive-mikev10
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: archive
Source: https://github.com/mikev10/olympus/tree/main/resources/skills/archive
Command: npx skills add https://github.com/mikev10/olympus --skill archive-mikev10

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of archiving completed AIDLC workflows, helping to keep the project directory clean and organized by moving completed tasks to a designated archive location.

Core Features & Use Cases

  • Workflow Archiving: Moves completed workflows from their active directory to a completed/ subdirectory.
  • Metadata Stamping: Updates workflow checkpoints with archival timestamps and paths.
  • Use Case: After a development cycle is finished and all tasks within a specific workflow are marked as complete, this Skill can be used to move that entire workflow's directory and associated files into an archive, preventing clutter in the active development area.

Quick Start

Use the archive skill to archive all completed workflows.

Frequently Asked Questions about archive

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

FAQPage Schema
How do I archive completed AIDLC workflows to keep my project directory organized?

To archive completed AIDLC workflows, the archive Skill scans for workflows with a complete status, moves them from the active directory to a designated completed subdirectory, and stamps them with archival metadata to ensure organized management of historical project data.

What is the process for moving completed workflows to an archive location?

The workflow archiving process involves scanning active project directories for completed AIDLC workflows, moving the entire workflow directory and associated files to a completed subdirectory, and updating project documentation with the new archival paths.

Does the archive Skill require any dependencies to stamp workflow metadata?

No dependencies are required to stamp workflow metadata. The archive Skill operates independently using its internal scripts to update workflow checkpoints with archival timestamps and paths during the organization process.

When should I use a workflow archiving script for completed development cycles?

You should use a workflow archiving script when a development cycle is finished and all tasks within a specific AIDLC workflow are marked complete, preventing clutter in the active development area by moving historical data to an archive.

Can I automate the organization of historical workflow data without manual file moves?

Yes, you can automate the organization of historical workflow data. The archive Skill automatically detects completed AIDLC workflows, moves them to a designated location, and updates project documentation without requiring manual file transfers.