openspec-archive-change

Archive completed openspec changes into dated directories after verifying tasks and syncing delta specs.

1|Updated Nov 3, 2023
One-click install
npx skills add https://github.com/luifertorres/trading-assistant --skill openspec-archive-change-luifertorres
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/luifertorres/trading-assistant/tree/main/.cursor/skills/openspec-archive-change
Command: npx skills add https://github.com/luifertorres/trading-assistant --skill openspec-archive-change-luifertorres

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the finalization and archival of completed changes in an openspec experimental workflow by verifying artifacts and tasks, assessing delta spec synchronization, and safely moving the change directory into a dated archive while preserving metadata.

Core Features & Use Cases

  • Guided Selection: Prompts the user to select an active change when a name is not provided, showing only non-archived changes and available schemas.
  • Completion Checks: Runs openspec status and reads tasks files to detect incomplete artifacts or checklist items, warning the user and requiring confirmation to proceed.
  • Delta Spec Assessment & Sync: Compares delta specs in openspec/changes/<name>/specs with main specs, summarizes adds/modifications/removals, and offers options to sync before archiving.
  • Safe Archival: Creates openspec/changes/archive, prevents overwriting existing archives, preserves .openspec.yaml, and moves the change to openspec/changes/archive/YYYY-MM-DD-<name>.
  • Use Case: Use this to finalize a feature or experiment after implementation to ensure specs and tasks are reconciled before moving the change into long-term archive.

Quick Start

Ask the skill to archive change 'my-change' after confirming artifacts, reviewing incomplete tasks, and choosing whether to sync delta specs.

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 an openspec workflow?

To archive completed changes in an openspec workflow, you select an active change, verify artifact and task completion, optionally sync delta specs, and move the directory into a dated archive folder. The process requires openspec CLI access to run status commands safely.

What happens to incomplete tasks when archiving an openspec change?

When archiving an openspec change with incomplete tasks, the process detects incomplete artifacts or checklist items by reading tasks markdown and warns you. It requires explicit user confirmation before proceeding with the finalization and archival.

Do I need to sync delta specs before moving changes to the archive directory?

Syncing delta specs before moving changes to the archive is optional. The process compares change specs with main specs to summarize additions, modifications, and removals, offering options to sync before finalizing the archive.

How does openspec change archival handle existing directories and metadata?

Openspec change archival prevents overwriting existing archives by creating a unique dated directory structure. It safely moves the change while preserving the .openspec.yaml metadata file during the filesystem operation.

Can I use the openspec CLI to list active changes before archiving?

Yes, you can use the openspec CLI to run list commands before archiving. The workflow parses JSON outputs from the CLI to show only non-archived changes and available schemas for guided selection.