skills.rest
edwardsnjd
edwardsnjdCOMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Archive completed changes after verifying artifact and task status with the openspec CLI.

9|1|Updated Jun 6, 2018
Search Tags:#workflow#archive#change management#openspec#task completion#specification sync
One-click install
npx skills add https://github.com/edwardsnjd/dot-files --skill openspec-archive-change-edwardsnjd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/edwardsnjd/dot-files/tree/main/configuration/agents/.agents/skills/openspec-archive-change
Command: npx skills add https://github.com/edwardsnjd/dot-files --skill openspec-archive-change-edwardsnjd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of archiving completed changes within an experimental workflow, ensuring a clean and organized project history.

Core Features & Use Cases

  • Automated Archiving: Moves completed changes to a designated archive location.
  • Status Verification: Checks artifact and task completion before archiving.
  • Delta Spec Sync: Assesses and optionally syncs delta specifications with main specifications.
  • Use Case: After implementing a new feature and testing it, use this Skill to archive the associated change, ensuring all related artifacts and tasks are accounted for and specifications are up-to-date.

Quick Start

Use the openspec-archive-change skill to archive the change named 'feature-x'.

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

You can archive a completed change by verifying artifact and task completion status, optionally synchronizing delta specifications with main specifications, and moving the change to an archive directory.

What is the process for syncing delta specifications with main specifications?▼

Syncing delta specifications involves assessing the differences between experimental delta specs and main specifications, then optionally applying those changes to ensure project documentation is up-to-date before archiving.

Do I need the openspec CLI to verify task completion status before archiving?▼

Yes, the openspec CLI is required to perform status checks and artifact management, ensuring that all related tasks and artifacts are fully completed before the change is archived.

Can I move a completed change to an archive directory without verifying artifacts?▼

No, status verification is a mandatory step that checks artifact and task completion before archiving, ensuring a clean and organized project history with fully accounted artifacts.

When should I archive a change in my workflow?▼

You should archive a change after implementing a new feature and testing it, ensuring all related artifacts and tasks are accounted for and specifications are up-to-date before moving it to the archive.

Related Skills

Explore More Software Engineering Skills→
pertrai1pertrai1

openspec-archive-change

Archive completed changes after verifying artifacts, tasks, and delta specs.

Community
Intermediate
SchurupIK72SchurupIK72

merge-helper

Automate feature branch integration with validation and documentation updates.

Community
Advanced
rock-hurock-hu

openspec-archive-change

Archive completed openspec changes into dated paths after validating artifacts and tasks.

Community
Advanced
hellyaxshellyaxs

openspec-archive-change

Archive completed OpenSpec changes after validating artifacts and tasks.

Community
Advanced