speckit-archive

Name: speckit-archive
Availability: InStock
Author: OpsMill

Archive merged feature specifications into main project memory with changelog entries.

9|4|Updated May 13, 2025

Search Tags:#changelog #specification #constitution #memory #archive #traceability

Ready to run

npx skills add https://github.com/opsmill/infrahub-mcp --skill speckit-archive

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-archive
Source: https://github.com/opsmill/infrahub-mcp/tree/main/.agents/skills/speckit-archive
Command: npx skills add https://github.com/opsmill/infrahub-mcp --skill speckit-archive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archiving feature specifications into the main project memory after merges helps teams capture decisions, close gaps, and ensure a single source of truth aligns with the project constitution.

Core Features & Use Cases

Archive spec.md, plan.md, memory artifacts, and agent knowledge updates into main memory.
Detect and report constitution conflicts and gaps for remediation.
Generate a changelog entry and provide a traceable source tag.

Quick Start

Archive the feature specification from specs/{id}-feature-name into main memory, then update memory artifacts and traceability.

Frequently Asked Questions about speckit-archive

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

FAQPage Schema

How do I archive a merged feature specification into project memory?▼

To archive a merged feature specification into project memory, the Skill processes spec.md and plan.md files from specs/{id}-feature-name, updating memory artifacts and agent knowledge while enforcing ordering by existing IDs.

How does archiving feature specs ensure traceability and update the changelog?▼

Archiving feature specs ensures traceability by generating a changelog entry with a traceable source tag and recording a revision note for each modified memory artifact, maintaining a single source of truth.

Can I detect constitution conflicts when archiving specifications into memory?▼

Yes, you can detect constitution conflicts when archiving specifications. The Skill validates constitution compatibility during the memory artifact update process and reports identified conflicts and gaps for remediation.

What is the best way to maintain a single source of truth after merging feature specs?▼

The best way to maintain a single source of truth after merges is to automate the archiving of spec.md and plan.md into main memory, validating consistency against the project constitution and updating agent knowledge.

Do I need to manually order memory artifacts when archiving specifications?▼

No, manual ordering is not needed when archiving specifications. The Skill enforces ordering by existing IDs automatically, ensuring completeness and consistency when updating memory artifacts and generating changelog entries.