skills.rest
factorial-io
factorial-ioOFFICIAL
Explore all skills by this author →
Website𝕏@factorial_ioGitHub

openspec-archive-change

Finalize and archive completed changes by verifying artifacts and tasks.

14|1|Updated Oct 16, 2024
Search Tags:#archive#change management#openspec#task completion#artifact completion
One-click install
npx skills add https://github.com/factorial-io/scotty --skill openspec-archive-change-factorial-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/factorial-io/scotty/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/factorial-io/scotty --skill openspec-archive-change-factorial-io

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Manages the finalization and archiving of a completed change in the experimental workflow, ensuring all artifacts and tasks are complete before archiving.

Core Features & Use Cases

  • Finalization: Checks the status of artifacts and tasks to ensure they are complete before archiving.
  • Artifact Completion: Verifies that all artifacts for the change are completed.
  • Task Completion: Inspects the tasks file for any incomplete tasks.
  • Delta Spec Sync: Assesses the delta spec sync state and provides options for syncing.
  • Archiving: Moves the change to the archive directory upon completion.

Quick Start

Archive the completed change with 'openspec-archive-change'.

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 a completed change in OpenSpec?▼

To archive a completed change in OpenSpec, you use the openspec CLI to verify artifact and task completion, manage delta spec sync state, and move the finalized change to an archive directory.

What happens if my OpenSpec change has incomplete tasks or artifacts?▼

If an OpenSpec change has incomplete tasks or artifacts, the archiving process will block the change from moving to the archive directory until all required tasks and artifacts are verified as complete.

How does delta spec sync state affect OpenSpec change archiving?▼

Delta spec sync state is assessed during change archiving to ensure spec modifications are properly synchronized, providing options to sync before the change can be safely moved to the archive directory.

Do I need the openspec CLI installed to finalize and archive changes?▼

Yes, you need the openspec CLI installed and available in your environment, as it is required for change listing, status checking, and artifact management during the finalization workflow.

When should I finalize and archive a change in the experimental workflow?▼

You should finalize and archive a change in the experimental workflow when all associated tasks are complete, artifacts are finished, and delta spec sync states are resolved to maintain a clean project state.

Related Skills

Explore More Software Engineering Skills→
AdJIaAdJIa

openspec-apply-change

Automate OpenSpec change task execution with status checks and context loading.

Community
Advanced
fjpulidopfjpulidop
9

openspec-archive-change

Archive completed OpenSpec changes into a date-based directory with validation.

Community
Advanced
ywh0606ywh0606

opsx-verify

Verify OpenSpec changes for completion and readiness before archiving.

Community
Intermediate
rock-hurock-hu

openspec-archive-change

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

Community
Advanced