spexl-archive

Merge spexl change deltas into reference specs and archive them.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/a3lem/spexl --skill spexl-archive
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spexl-archive
Source: https://github.com/a3lem/spexl/tree/main/.claude/skills/spexl-archive
Command: npx skills add https://github.com/a3lem/spexl --skill spexl-archive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archiving completed spexl changes by merging deltas into the reference specs, while preserving history and keeping the reference specs as the source of truth.

Core Features & Use Cases

  • Merge deltas into reference specs to reflect completed changes.
  • Validate merged specs with the spec-critic agent and ensure consistency.
  • Move the archived change under specs/changes/archive/YYYY-MM-DD-slug/ preserving history.

Quick Start

Run the archive workflow for a completed change to merge deltas into reference specs and move the change to archive.

Frequently Asked Questions about spexl-archive

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

FAQPage Schema
How do I merge spec deltas into reference specs after a change is completed?

Merging spec deltas into reference specs requires applying completeness checks, folding the deltas into the source-of-truth references, validating the result, and relocating the change under the archive directory.

What is the best way to archive monorepo spec changes while preserving history?

The best way to archive monorepo spec changes is by merging deltas into reference specs and moving the completed change folder to a dated archive directory structured as specs/changes/archive/YYYY-MM-DD-slug/.

Does archiving spec changes validate the merged reference specs for consistency?

Yes, the archive process validates the merged reference specs for consistency using a spec-critic agent, ensuring the updated reference specs remain accurate and reliable as the single source of truth.

When do I need to archive a completed spec change in a monorepo workflow?

You need to archive a completed spec change in a monorepo workflow once the deltas are finalized, triggering the process to update the reference specs and relocate the change folder to the dated archive directory.

Can I use this archiving workflow without a spec validation agent?

The workflow is designed to validate merged specs with a spec-critic agent to ensure consistency. Bypassing this validation step risks introducing inconsistencies into the reference specs during the delta merge.