archive

Archive completed changes by passing an explicit change name or detecting prior work to the archive subagent. This preserves experiment artifacts and maintains a clean project history by reducing clutter in your active workspace.

Change management archiving preserves finalized experiment artifacts while removing them from active development. It keeps workflows tidy by moving completed changes out of the current scope while retaining project history.

Workflow automation supports archiving completed changes through a dedicated subagent. You can pass explicit user arguments to specify which changes to archive, or let the system detect existing change names from prior work automatically.

Manual specification is optional. The archive skill can detect an existing change name from prior work and pass it to the archive subagent automatically, or you can provide explicit user arguments to target a specific experiment for archiving.

The best way to keep workflows tidy is to archive completed changes immediately after finalization. This preserves artifacts and removes obsolete items from the active workspace by launching the archive subagent.

The archive subagent fails when it cannot detect an existing change name from prior work and no explicit user arguments are provided. You must supply a specific change name as an argument if prior workflow context is missing.