skills.rest
DanielShuguang
DanielShuguangCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-archive-change

Archive completed experimental changes and synchronize incremental specifications with main specifications.

1|Updated Jul 30, 2023
Search Tags:#workflow#version control#archive#openspec#specification management#experimental changes
One-click install
npx skills add https://github.com/DanielShuguang/tool-box --skill openspec-archive-change-danielshuguang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/DanielShuguang/tool-box/tree/main/.trae/skills/openspec-archive-change
Command: npx skills add https://github.com/DanielShuguang/tool-box --skill openspec-archive-change-danielshuguang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec-cn, openspec-sync-specs, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of archiving completed experimental changes within a workflow, ensuring a clean and organized record of development.

Core Features & Use Cases

  • Automated Archiving: Safely archives experimental changes after completion.
  • Status Verification: Checks artifact and task completion before archiving.
  • Spec Synchronization: Facilitates synchronization of incremental specifications with main specifications.
  • Use Case: After finishing a new feature implementation and ensuring all related tasks and artifacts are complete, use this skill to formally archive the change, making it a permanent part of the project history.

Quick Start

Archive the experimental change named 'feature-x-implementation'.

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 experimental changes in a workflow?▼

To archive completed experimental changes, you use a workflow process that verifies all artifacts and tasks are finalized, synchronizes incremental specifications with main specifications, and then archives the change using the openspec CLI.

What happens to incremental specifications when archiving an experimental change?▼

When archiving an experimental change, the workflow facilitates the synchronization of incremental specifications with main specifications, ensuring the finalized updates are merged into the main project history before the archive is completed.

Do I need the openspec CLI to manage specification archiving?▼

Yes, you need the openspec CLI to manage changes and specifications, as it is a required dependency for verifying task completion and executing the archiving of experimental changes.

When should I archive an experimental change in specification management?▼

You should archive an experimental change in specification management only after finishing a new feature implementation and ensuring all related artifacts and tasks are complete, making it a permanent part of the project history.

Does archiving experimental changes verify task completion?▼

Yes, archiving experimental changes includes status verification to check that all related artifacts and tasks are complete before the workflow safely archives the finalized specifications.

Related Skills

Explore More Software Engineering Skills→
dariopalminiodariopalminio
1

openspec-generate-baseline

Generate an OpenSpec baseline from existing source code and archive it.

Community
Advanced
yandiaanyandiaan
2

openspec-sync-specs

Merge delta specification changes into main capability specs.

Community
Advanced
rfhaynrfhayn
2

openspec-archive-change

Archive experimental openspec changes after verifying task and artifact completion.

Community
Advanced
VIethoangnguyenleVIethoangnguyenle

openspec-archive-change

Verify, synchronize, and archive completed workflow changes with the openspec CLI.

Community
Intermediate