skills.rest
javakishore-veleti
javakishore-veletiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-bulk-archive-change

Archive multiple completed OpenSpec changes with conflict-aware spec synchronization.

Updated Aug 7, 2026
Search Tags:#cli#archive#conflict resolution#change management#spec-driven development#openspec#batch workflow
One-click install
npx skills add https://github.com/javakishore-veleti/lifting-diary-app --skill openspec-bulk-archive-change-javakishore-veleti
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/javakishore-veleti/lifting-diary-app/tree/main/.qwen/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/javakishore-veleti/lifting-diary-app --skill openspec-bulk-archive-change-javakishore-veleti

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Archiving several completed OpenSpec changes one at a time is slow and error-prone, especially when multiple changes touch the same capability spec. This Skill batches the entire archive workflow, detects spec conflicts between changes, and resolves them by checking what is actually implemented in the codebase. ## Core Features & Use Cases - Batch archiving: Select and archive multiple active changes in one confirmed operation, with per-change status tracking for artifacts, tasks, and delta specs. - Conflict detection and resolution: Identifies when two or more changes modify the same capability spec path, inspects the codebase for implementation evidence, and applies delta specs in chronological order or skips unimplemented ones. - Verified spec sync: Syncs included delta specs into main specs and verifies ADDED, MODIFIED, REMOVED, and RENAMED requirements before moving any change into the archive directory. - Use Case: After finishing a sprint with five parallel feature changes, run this Skill to review a consolidated status table, resolve a conflict on the identity/user-auth spec, and archive all ready changes with date-prefixed directory names in one confirmation. ## Quick Start Ask the assistant to bulk archive all completed OpenSpec changes and confirm the batch when shown the status table.

Frequently Asked Questions about openspec-bulk-archive-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I archive multiple OpenSpec changes at once?▼

Run the bulk archive workflow, which lists all active changes, prompts you to multi-select the ones to archive, shows a consolidated status table, and archives the confirmed set in one operation. Each change is moved to the archive directory with a YYYY-MM-DD prefixed name.

How are spec conflicts resolved when archiving parallel changes?▼

Conflicts are detected when two or more selected changes have delta specs for the same capability path. The workflow reads each delta spec, searches the codebase for implementation evidence, then syncs only implemented changes, applying both in chronological order when both are implemented.

Does bulk archive work with OpenSpec stores?▼

Yes. If the work lives in a registered store, the workflow discovers store ids with openspec store list --json and passes --store <id> on all commands that read or write specs and changes. Without a store, commands act on the nearest local openspec root.

What happens if a change has incomplete tasks during bulk archive?▼

Incomplete changes are flagged in the status table with warnings showing incomplete artifacts and task counts. You can choose to archive everything, archive only ready changes and skip the rest, or cancel the entire batch.

Why would a delta spec sync be skipped during archiving?▼

A delta spec sync is skipped when conflict resolution finds no implementation evidence for that change in the codebase. The skip is reported per delta with the change name, capability path, and reason, while the change itself can still be archived.

Related Skills

Explore More Software Engineering Skills→
ybenitezfybenitezf

openspec-archive-change

Archive completed OpenSpec changes to a dated directory while preserving .openspec.yaml.

Community
Advanced
TencentBlueKingTencentBlueKing
840

openspec-sync-specs

Sync delta specs from an OpenSpec change into main specification files.

Official
Intermediate
firstsun-devfirstsun-dev
3

openspec-verify-change

Verify implementation matches OpenSpec change artifacts before archiving.

Official
Advanced
RuixeWolfRuixeWolf
4

openspec-bulk-archive-change

Archives multiple completed OpenSpec changes in one batch with conflict-aware spec syncing.

Community
Advanced