source-command-opsx-archive

Archives completed OpenSpec changes after syncing delta specs and verifying merged pull requests.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/Marcel-Carrillo/ProyectosIA --skill source-command-opsx-archive-marcel-carrillo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-command-opsx-archive
Source: https://github.com/Marcel-Carrillo/ProyectosIA/tree/main/.agents/skills/source-command-opsx-archive
Command: npx skills add https://github.com/Marcel-Carrillo/ProyectosIA --skill source-command-opsx-archive-marcel-carrillo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Completed OpenSpec changes accumulate in the active changes directory, leaving delta specs unsynced with main specs, uncommitted archive moves, stale Git worktrees, and Jira tickets stuck in the wrong status. ## Core Features & Use Cases - Validated archival: Checks artifact and task completion via openspec status --json, warns on incomplete items, and moves the change to openspec/changes/archive/YYYY-MM-DD-<name>/ using the native CLI. - Mandatory spec sync: Automatically applies delta specs to main specs through the openspec-sync-specs skill before archiving, aborting if the sync fails. - Delivery verification and close-out: Confirms the change's PR is merged via gh pr list, commits the sync and archive results, offers Git worktree cleanup, and transitions the linked Jira ticket to "Finalizado". - Use Case: After merging the PR for a change like add-auth, run the archive command to sync its delta specs into openspec/specs/, move the change folder into the dated archive, commit everything, and close the Jira ticket in one guided flow. ## Quick Start Ask the assistant to archive the completed OpenSpec change named add-auth and confirm any warnings about incomplete tasks or artifacts.

Frequently Asked Questions about source-command-opsx-archive

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

FAQPage Schema
How do I archive a completed OpenSpec change?▼

Run the archive command with the change name, for example /opsx:archive add-auth. The workflow checks artifact and task completion, syncs delta specs, then runs openspec archive <name> --skip-specs -y to move the change into the dated archive directory.

What happens if delta specs exist when archiving an OpenSpec change?▼

Delta spec sync is mandatory and runs automatically without asking. The workflow invokes the openspec-sync-specs skill to apply additions, modifications, and removals to the main specs, and aborts the archive entirely if the sync fails.

Can I archive an OpenSpec change with incomplete tasks?▼

Yes, but the workflow counts incomplete tasks marked with - [ ] in tasks.md and displays a warning requiring your confirmation before proceeding. The same confirmation flow applies to incomplete artifacts reported by openspec status --json.

Does the archive workflow verify the pull request is merged?▼

Yes, it runs gh pr list --state merged --search with the change name to confirm delivery. If no merged PR is found, it warns that the change does not appear delivered and asks for confirmation before continuing.

Why does OpenSpec archive fail with target directory already exists?▼

The CLI fails when an archive folder with the same date and change name already exists under openspec/changes/archive/. Rename or delete the existing archive, or wait until a different date to archive.

Does archiving update the linked Jira ticket status?▼

Yes, if the archived change directory contains a .jira file with a ticket key, the workflow transitions it to Finalizado using the Jira REST API with Atlassian credentials, falling back to adding a comment via the Atlassian MCP tool.