skills.rest
fkoschi
fkoschiCOMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Archives completed changes in the experimental workflow after verifying artifacts and tasks.

2|Updated Nov 14, 2024
Search Tags:#workflow#task management#archive#change management#openspec#specification sync
One-click install
npx skills add https://github.com/fkoschi/grind-it --skill openspec-archive-change-fkoschi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/fkoschi/grind-it/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/fkoschi/grind-it --skill openspec-archive-change-fkoschi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (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 thoroughly, use this Skill to archive the 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 'user-authentication-flow'.

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

To archive completed changes in an openspec workflow, use this skill to move finished changes to a designated archive location after verifying that all related artifacts and tasks are fully complete.

What happens to incomplete tasks when archiving a change?▼

When archiving a change with incomplete tasks, the skill handles user confirmation prompts to ensure you intentionally archive items that still have pending artifacts or unfinished task requirements.

How does specification sync work when archiving a change in openspec?▼

Specification sync during archiving assesses delta specifications and optionally merges them with main specifications, ensuring your project documentation stays up-to-date after moving the change to the archive.

Do I need the openspec CLI to archive completed changes?▼

Yes, you need the openspec CLI installed and available in your environment, as the archiving process relies on it to verify completion statuses and execute the specification sync operations.

When should I archive a change instead of keeping it active in task management?▼

You should archive a change after thoroughly implementing and testing a new feature, ensuring all related artifacts and tasks are accounted for and specifications are synced to maintain a clean project history.

Related Skills

Explore More Software Engineering Skills→
formioformio
6

openspec-archive-change

Archive completed changes in an openspec experimental workflow.

Official
Intermediate
statick88statick88
1

sdd-archive

Merge delta specifications into main specs and archive completed change folders.

Community
Advanced
TranVanTienDatTranVanTienDat

openspec-archive-change

Archive completed changes with openspec CLI after completion checks.

Community
Intermediate
rock-hurock-hu

openspec-archive-change

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

Community
Advanced