omos-archive

Archive completed OpenSpec changes by delegating to the bundled vendored archive skills — the Codex twin of OpenCode's archive command. Every instruction line below is rendered from archiveInstruction in core/prompts.ts, the same single source the OpenCode command prompts with; the only transforms are the id-count branches pinned statically and the skill names in the load lines rendered as $-mentions.

Arguments arrive as plain text in the user's message after the $oh-my-openspec:omos-archive mention — there is no argument substitution. Split the message on whitespace into change ids and follow the branch the id count selects (the archiveSkillId mapping: zero or one id binds the single-archive skill, two or more bind the bulk one):

• Zero ids — Load the $openspec-archive-change skill and follow it exactly. No change ids given — list active changes, confirm with the user which to archive.
• One id — Load the $openspec-archive-change skill and follow it exactly. Change: <change-id>
• Two or more ids — Load the $openspec-bulk-archive-change skill and follow it exactly. Changes: <id-1>, <id-2>

Follow each branch's steps in order:

Validate first with the openspec_validate tool; stop on INVALID unless the user explicitly overrides. Use the delegated archive skill for its other checks. These plugin-mandated steps override any conflicting upstream sync or archive choices: do not ask whether to sync, and stop before archiving if required sync is blocked. Sync the selected change's specification deltas into the main specs before archiving; do not ask whether to sync. When sync creates a new openspec/specs/<capability>/spec.md, give it a readable top-level title derived from the capability's purpose or meaning. Preserve existing authored titles and machine-named capability paths. If required specification sync is blocked, stop without archiving and report the blocker. After archiving, validate the resulting specifications. Repair issues that are safely fixable within OpenSpec artifacts, then validate again. If a post-archive issue requires code changes or cannot be safely repaired within OpenSpec artifacts, stop and report it without claiming validation passed.