archive

To archive completed experimental changes, trigger the archive subagent by passing the change name or explicit arguments to preserve artifacts, specs, and verification outcomes for future reference and auditing.

Preserving artifacts after implementing an experimental change requires triggering an automated archive workflow that retains relevant specs and verifications, keeping project history tidy and auditable for future retrieval.

You need to archive experimental changes when a change is finalized and needs preservation, ensuring prior spec, implementation, and verification artifacts are retained for easy retrieval and project auditing.

Yes, you need to pass the change name or explicit arguments to the archive subagent to identify the target change and initiate the archiving process with the appropriate context.

Yes, you can automate the archiving of specs and verification artifacts by prompting the AI to trigger the archive subagent, which identifies the target change and preserves the context automatically.

The archiving workflow is designed for finalizing and preserving completed experimental changes, meaning it applies to scenarios where changes need to be finalized rather than actively developed or modified.