skills.rest
Quafadas
QuafadasCOMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Archive completed OpenSpec changes after validating artifacts, tasks, and delta specs.

13|2|Updated Apr 1, 2024
Search Tags:#archive#openspec#change-management#artifact-tracking#task-status#delta-specs
One-click install
npx skills add https://github.com/Quafadas/live-server-scala-cli-js --skill openspec-archive-change-quafadas
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/Quafadas/live-server-scala-cli-js/tree/main/.github/skills/openspec-archive-change
Command: npx skills add https://github.com/Quafadas/live-server-scala-cli-js --skill openspec-archive-change-quafadas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archiving completed OpenSpec changes after ensuring artifacts are finalized, tasks are complete, and delta specs are in sync, so teams can maintain a clean audit trail.

Core Features & Use Cases

  • Validate artifact completion with openspec status and identify any incomplete artifacts before archiving.
  • Check pending tasks in tasks.md and prompt for confirmation if there are any open items.
  • Assess delta specs against main specs and optionally synchronize them before archival.
  • Preserve the original change directory (including .openspec.yaml) while moving it into an archive folder for auditability.

Quick Start

Provide a change name when prompted and confirm archival steps to complete the process.

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 OpenSpec changes while maintaining an audit trail?▼

Archive completed OpenSpec changes by validating artifacts, checking task completion, and moving the change directory into a dated archive folder at openspec/changes/archive/YYYY-MM-DD-<name>. This preserves the original .openspec.yaml file for auditability.

What steps are required to finalize and archive delta specs in OpenSpec?▼

To archive delta specs, the process checks pending tasks in tasks.md, assesses delta specs against main specs, and optionally synchronizes them before moving the change into the archive directory to ensure a clean audit trail.

Does OpenSpec archival check for incomplete artifacts before moving changes?▼

Yes, OpenSpec archival validates artifact completion using openspec status to identify any incomplete artifacts. It also checks pending tasks in tasks.md and prompts for confirmation if there are open items before proceeding.

Why does my OpenSpec change directory structure need to be preserved during archival?▼

Preserving the original change directory, including the .openspec.yaml file, during archival maintains a clean audit trail. It ensures historical context and configuration data remain intact within the dated archive folder structure.

What happens if I try to archive an OpenSpec change with open tasks in tasks.md?▼

If there are pending tasks in tasks.md, the archival process will detect the open items and prompt for confirmation before proceeding, ensuring incomplete work is not accidentally moved into the dated archive.

Related Skills

Explore More Software Engineering Skills→
fkoschifkoschi
2

openspec-verify-change

Verify code implementations match specified Openspec change artifacts and generate a detailed report.

Community
Advanced
joannanowakowskajoannanowakowska

openspec-archive-change

Archive completed OpenSpec changes after validating artifacts and task completion.

Community
Advanced
ilazinessilaziness
6

openspec-archive-change

Archive completed OpenSpec changes after validating tasks and syncing delta specs.

Community
Advanced
KisthannyKisthanny
1

openspec-archive-change

Archive completed OpenSpec change directories after validating readiness and preserving workflow context.

Community
Advanced