archive

Finalizes Beat changes by syncing features to living documentation and archiving them.

7|3|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/kirkchen/beat --skill archive-kirkchen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: archive
Source: https://github.com/kirkchen/beat/tree/main/skills/archive
Command: npx skills add https://github.com/kirkchen/beat --skill archive-kirkchen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive a completed Beat change by validating completion, syncing features to living documentation, and moving artifacts to the archive, ensuring governance and traceability.

Core Features & Use Cases

  • Pre-archive checks to ensure readiness and prevent missed steps.
  • Automatic synchronization of beat/features with living documentation and associated proposal/design notes.
  • Post-archive governance with optional finishing-a-development-branch guidance.

Quick Start

Run the archive workflow to finalize a change, sync features, archive the change, and trigger post-archive governance.

Frequently Asked Questions about archive

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

FAQPage Schema
How do I archive completed changes and sync living docs automatically?

To archive completed changes and sync living docs, this workflow runs pre-archive checks, synchronizes beat/features with living documentation, and moves artifacts into an archive. It ensures governance and traceability for finalized changes.

What is the best way to finalize a development branch and update status.yaml?

Finalizing a development branch involves reading and updating status.yaml, validating optional tasks, and triggering post-archive governance. This workflow optionally invokes a finishing-a-development-branch superpower to manage the process end-to-end.

Can I validate tasks before moving features to the archive?

Yes, you can validate tasks before archiving. The workflow applies pre-archive checks to ensure readiness and performs optional task validation, preventing missed steps before synchronizing features and moving artifacts to the archive.

How does feature synchronization work with living documentation and design notes?

Feature synchronization automatically updates living documentation and associated proposal or design notes. It manages the beat/features structure directly, ensuring all related artifacts reflect the finalized change before archiving.

Does the archive workflow handle .orig backups during change management?

Yes, the archive workflow handles .orig backups during change management. It manages the beat/features structure and processes these backups as part of the end-to-end archiving workflow for governance and traceability.

What post-archive governance steps are applied after syncing living docs?

Post-archive governance steps are applied after syncing living docs to maintain traceability. The workflow optionally provides finishing-a-development-branch guidance to ensure all governance requirements are met following the archival process.