skills.rest
Miss-PinkElf
Miss-PinkElfCOMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Archive completed SPARK changes after review and verification with closure summaries.

Updated Apr 2, 2026
Search Tags:#verification#review#archive#change-management#delta-sync#spark-workflow
One-click install
npx skills add https://github.com/Miss-PinkElf/Multi-Agent --skill openspec-archive-change-miss-pinkelf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/Miss-PinkElf/Multi-Agent/tree/main/.claude/skills/spark-workflow/skills/openspec-archive-change
Command: npx skills add https://github.com/Miss-PinkElf/Multi-Agent --skill openspec-archive-change-miss-pinkelf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines closing a SPARK change lifecycle by ensuring changes are archived only after verification and review are complete, preventing premature closure.

Core Features & Use Cases

  • Post-review archiving: Safely archive completed changes after verification.
  • Delta synchronization checks: Ensure delta specs are synced back to the main spec set or record the closure if needed.
  • Audit-ready summaries: Generate a concise recap of shipped work and passed evidence.

Quick Start

Archive the completed SPARK change after all reviews pass and tasks are verified.

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 SPARK changes after verification and review?▼

To archive SPARK changes after verification, confirm the change identity, verify artifact and task completion, and generate a succinct closure summary to ensure proper record-keeping in the SPARK-workflow lifecycle.

What is the SPARK-workflow change archiving process?▼

The SPARK-workflow change archiving process formally closes completed changes by archiving artifacts, documenting what shipped, and ensuring delta specs are synced back to the main spec set after review.

Do I need to verify all tasks before archiving a SPARK change?▼

Yes, you need to verify all tasks before archiving a SPARK change. Guardrails prevent premature archiving by requiring artifact and task completion checks alongside review confirmation.

How do delta synchronization checks work when archiving completed changes?▼

Delta synchronization checks ensure delta specs are synced back to the main spec set or record the closure if needed, maintaining consistency across the SPARK-workflow during the archiving process.

Can I generate an audit summary for shipped SPARK-workflow changes?▼

Yes, you can generate an audit-ready summary for shipped SPARK-workflow changes. The archiving process produces a concise recap of shipped work and passed evidence for record-keeping.

Why does premature archiving fail in SPARK-workflow change management?▼

Premature archiving fails because guardrails require confirmation of change identity and completion of artifact and task checks, preventing changes from closing before verification and review are fully complete.

Related Skills

Explore More Software Engineering Skills→
ruan-catruan-cat
4

openspec-archive-change

Archive completed changes into dated folders under openspec/changes/archive.

Community
Intermediate
mufengbufengmufengbufeng
1

openspec-sync-specs

Apply ADDED, MODIFIED, REMOVED, and RENAMED delta changes to main specs.

Community
Intermediate
bruinalphainvestmentbruinalphainvestment

openspec-archive-change

Finalize and archive completed changes using the openspec CLI.

Official
Intermediate
accidental-hedge-fundaccidental-hedge-fund
3

openspec-archive-change

Archive completed openspec experimental changes to dated directories with validation.

Official
Intermediate