openspec-archive-change

Automate archiving completed changes in an experimental workflow.

3|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/tenondecrpc/tempo-for-claude --skill openspec-archive-change-tenondecrpc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/tenondecrpc/tempo-for-claude/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/tenondecrpc/tempo-for-claude --skill openspec-archive-change-tenondecrpc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides an organized process for finalizing and archiving completed changes in an experimental workflow, simplifying the workflow maintenance for the user.

Core Features & Use Cases

  • Archive Changes: Securely store finalized changes for easy future reference.
  • Automated Workflow: Streamlines the finalization of experimental workflow changes with minimal user interaction.
  • Use Case: Ideal for project managers and team leads who need to maintain a record of changes in an iterative workflow.

Quick Start

Archive the most recent change with 'archive-change'

Frequently Asked Questions about openspec-archive-change

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

FAQPage Schema
How do I archive completed changes in a software development lifecycle?

You can archive completed changes by running the 'archive-change' command, which automates the finalization of experimental workflow entries for finalized features and bug fixes.

What is the best way to automate finalizing features and bug fixes in an iterative workflow?

Automating finalization is handled by this change archiving process, which streamlines storing completed change entries with minimal user interaction for future reference.

When do I need to archive change entries in project maintenance?

Archive change entries when finalized features or bug fixes are complete and you need to securely store them as a record for easy future reference in project maintenance.

Can I use automated change archiving for experimental software workflows?

Yes, automated change archiving is specifically designed to support project management tasks within an experimental software workflow, organizing the finalization process for completed changes.

Does change archiving require manual input for each completed task?

No, change archiving minimizes user interaction by automating the workflow, allowing you to effortlessly archive the most recent change with a single command.

What limitations exist when archiving changes in an iterative workflow?

The archiving process is tailored for experimental workflows and finalized change entries, meaning it is specialized for project maintenance rather than general software development tasks.