Agent-Skills.md

Agent Skills: OpenSpec Archive Change

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

UncategorizedID: u473t8/learning-app/openspec-archive-change

Repository

u473t8/learning-app
u473t8

Install this agent skill to your local

pnpm dlx add-skill https://github.com/u473t8/learning-app/tree/HEAD/.codex/skills/openspec-archive-change

Skill Files

Browse the full folder contents for openspec-archive-change.

Download Skill

Loading file tree…

.codex/skills/openspec-archive-change/SKILL.md

Skill Metadata

Name
openspec-archive-change
Description
Archive a completed OpenSpec change using the current OpenSpec CLI. Use this when the user wants to finalize work, update main specs as part of archiving, and close out a change cleanly.

OpenSpec Archive Change

Use this skill when the user wants to archive a completed change.

Workflow

  1. Resolve the target change.

    • Prefer the user-provided name.
    • Otherwise inspect active changes and ask only if more than one candidate remains.

  2. Inspect change completion:

OPENSPEC_TELEMETRY=0 openspec status --change "<name>" --json

  1. Read the tasks artifact if it exists and note incomplete checkboxes.

  2. Warn about incomplete artifacts or tasks before archiving.

    • If the user still wants to proceed, continue.

  3. Archive with the built-in CLI:

OPENSPEC_TELEMETRY=0 openspec archive "<name>"

Useful variants:

  • OPENSPEC_TELEMETRY=0 openspec archive "<name>" --skip-specs for tooling, infra, or doc-only changes
  • OPENSPEC_TELEMETRY=0 openspec archive "<name>" -y when the user already explicitly confirmed archiving
  1. Summarize:
    • archive result
    • whether specs were updated or skipped
    • whether any warnings were overridden

Notes

  • Prefer the built-in openspec archive command over manual file moves.
  • If the user wants delta specs synced without archiving, use openspec-sync-specs instead.
  • Archive before the delivery PR is opened or merged, so implementation, spec updates, and archive move land in one PR.
  • Do not push archive commits directly to master; if archive was missed before merge, create a follow-up PR and report the workflow miss.
  • OpenSpec CLI includes PostHog telemetry. Use OPENSPEC_TELEMETRY=0 by default. If PostHog flush/network errors appear after a successful command, treat them as telemetry noise.