mspec-archive

Merge changes into the source-of-truth spec and archive them.

4|Updated May 13, 2026
One-click install
npx skills add https://github.com/tubone24/mspec --skill mspec-archive
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mspec-archive
Source: https://github.com/tubone24/mspec/tree/main/.claude/skills/mspec-archive
Command: npx skills add https://github.com/tubone24/mspec --skill mspec-archive

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The mspec-archive Skill automates the archiving process within the mspec workflow, which ensures the deterministic merging of changes into the SoT spec and archives.

Core Features & Use Cases

  • Archive Merge: Deterministically merges changes into the source-of-truth spec.
  • Post-Mortem Analysis: Analyzes the lessons learned from the change and identifies follow-up actions.
  • Purpose Auto-Generation: Automatically generates the purpose field for the archived capabilities.

Quick Start

To run the archive step of the mspec workflow, use the command: /mspec:archive

Frequently Asked Questions about mspec-archive

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

FAQPage Schema
How do I automate archiving changes into a source-of-truth specification?▼

To automate specification archiving, you can use the mspec-archive Skill, which deterministically merges tracked changes into your source-of-truth spec and archives them for record-keeping.

What is the best way to generate a post-mortem after updating a specification?▼

Generating a specification post-mortem involves analyzing lessons learned from the change, which the archive process handles automatically using the mspec-lessons-analyzer subagent to identify follow-up actions.

How does automatic purpose generation work for archived capabilities?▼

Automatic purpose generation works by evaluating the merged changes during the archive step and auto-generating a purpose field for the newly archived capabilities to maintain clear specification context.

Can I track lessons learned and next actions when merging code specifications?▼

Yes, you can track lessons learned and next actions during specification merges by utilizing the mspec-nextaction-planner subagent, which identifies required follow-up actions post-archiving.

Do I need any dependencies to run the mspec workflow archive step?▼

No external dependencies are required to run the mspec workflow archive step, as the Skill operates independently using its internal scripts and subagents to manage the archiving process.

When should I use an automated archive step for specification change tracking?▼

You should use an automated archive step for specification change tracking when you need deterministic merging into your source-of-truth spec and want to automatically capture lessons learned and capability purposes.