eo-archive

Merge approved Spec Deltas into a module's spec.md and archive the change.

30|5|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/SimpleEve/eo-skills --skill eo-archive
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eo-archive
Source: https://github.com/SimpleEve/eo-skills/tree/main/eo-archive
Command: npx skills add https://github.com/SimpleEve/eo-skills --skill eo-archive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the final archival step of a change lifecycle by merging approved Spec Deltas into a module's spec.md, preventing manual drift and ensuring the project's living specification stays current and auditable.

Core Features & Use Cases

  • Delta-driven merging: consumes ADDED / MODIFIED / REMOVED entries from the change.md "## 3 Spec Delta" section and applies them mechanically to the target spec.md.
  • Validation and safety checks: verifies change status is done, review and test artifacts exist and passed, enforces single-module scope, and aborts on format or cross-module conflicts.
  • Metadata & index updates: updates spec frontmatter updated date, appends entries to 关联变更 and 变更记录 sections, sets change.md status to archived, and updates module and global INDEX files.
  • Use case: finalize a completed feature change by merging its declared Deltas into a module's spec.md, update history, and mark the change archived without manual edits.

Quick Start

Run the archive operation for module inventory change 015-add-sort by invoking /eo-archive inventory 015-add-sort

Frequently Asked Questions about eo-archive

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

FAQPage Schema
How do I merge approved spec deltas into a module's spec.md?

To merge spec deltas into spec.md, apply ADDED, MODIFIED, and REMOVED entries from the change.md Delta section mechanically, then update frontmatter, index metadata, and set the change status to archived.

What is delta-driven merging for living specifications?

Delta-driven merging consumes ADDED, MODIFIED, and REMOVED entries from a change.md file and applies them mechanically to a target spec.md, ensuring the project specification stays current and auditable without manual edits.

What prerequisites are needed to archive a change in an eo-doc workflow?

Archiving a change requires the change.md status to be done, review to be passed, and optional test results to exist, while enforcing single-module scope to prevent cross-module conflicts during the spec.md merge.

Does the spec archival process abort on cross-module conflicts?

Yes, the archival process detects cross-module or format conflicts and aborts automatically for user decision, ensuring safety checks prevent manual drift when applying change deltas to the target spec.md.

Can I update module and global index metadata when archiving changes?

Yes, the archival process updates spec frontmatter dates, appends entries to change history sections, sets change.md status to archived, and updates both module and global INDEX files to finalize the change.

What is the best way to finalize a completed feature change in single-module eo-doc development?

The best way to finalize a completed feature change is to invoke the archive operation on the specific module and change ID, mechanically merging declared deltas into spec.md and marking the change archived.