cash-archive

Validate artifact status and task completion before archiving project changes.

1|Updated May 11, 2026

Search Tags:#automation #git #workflow #task management #sync #archive

Ready to run

npx skills add https://github.com/cashwu/Agentflow-SDD --skill cash-archive

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cash-archive
Source: https://github.com/cashwu/Agentflow-SDD/tree/main/.agents/skills/cash-archive
Command: npx skills add https://github.com/cashwu/Agentflow-SDD --skill cash-archive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the complex, multi-step process of archiving completed project changes, ensuring that task statuses, artifact completion, and delta specifications are correctly validated and synchronized.

Core Features & Use Cases

Automated Validation: Verifies artifact completion and task status before archiving to prevent premature closure.
Spec Synchronization: Manages the delta specification lifecycle, allowing users to sync or skip specs during the archive process.
Use Case: When a developer finishes a feature branch, they can use this skill to safely move the change to the archive directory while ensuring all documentation and task lists are finalized and consistent.

Quick Start

Use the cash-archive skill to archive the completed change named add-auth.

Frequently Asked Questions about cash-archive

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

FAQPage Schema

How do I automate project change archival and sync for completed Git branches?▼

Automating project change archival requires validating artifact status and task completion before moving changes to an archive directory. This process synchronizes delta specifications and ensures a consistent directory structure for maintaining accurate project history.

How does artifact validation work before archiving project changes?▼

Artifact validation checks task completion and artifact status before archiving to prevent premature closure of project changes. It verifies that all documentation and task lists are finalized and consistent before moving the feature branch to the archive directory.

Do I need a local Git root and Cash CLI launcher to run transactional archive operations?▼

Yes, executing transactional archive operations requires a project-local Git root and a valid Cash CLI launcher. These dependencies ensure the skill can safely validate artifacts and synchronize delta specifications during the archival process.

What is the best way to manage delta specification lifecycle during task archival?▼

Managing the delta specification lifecycle during task archival involves synchronizing or skipping specs as needed. This ensures delta specifications remain consistent with the archived project changes and maintains accurate historical records.

When should I not use automated workflow archival for project changes?▼

You should not use automated workflow archival when artifact completion or task statuses are still pending. Archiving prematurely bypasses the validation checks that ensure all documentation and task lists are properly finalized before moving changes.