eo-change

Plan and execute module-level changes with Delta declarations in change documents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates module-level change management by producing a Delta-backed change document that ties a proposed change to the module spec and plan, enabling clear traceability and incremental evolution without overwriting the living spec.

Core Features & Use Cases

  • Treat modules as first-class citizens with a centralized location under eo-doc/dev/<module-name>/changes
  • Declare Delta (ADDED / MODIFIED / REMOVED) without rewriting the spec during change progression
  • Generate a concrete change.md per change, then archive to apply Delta back into the spec
  • Support bootstrap, feature/enhance/refactor workflows and handle cross-module scenarios when multiple specs are affected
  • Provide a unified template-driven workflow from draft to archive, ensuring traceability and reproducibility

Quick Start

Create a new change document under eo-doc/dev/<module-name>/changes, draft change.md following the template, and start the eo-change workflow.

Frequently Asked Questions about eo-change

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

FAQPage Schema
How do I track module spec changes without overwriting the living documentation?

Module spec changes are tracked by declaring a Delta of ADDED, MODIFIED, or REMOVED items in a dedicated change document. This ties the proposed change to the living spec without rewriting it during change progression.

How do I manage cross-module changes when multiple specs are affected?

Cross-module changes are managed by creating change documents that reference multiple affected module specs. The workflow supports cross-module scenarios by declaring Deltas across all impacted specs within a single coordinated change plan.

Do I need an initialized spec.md file before starting a module change workflow?

Yes, an initialized module spec file is required before starting. The workflow requires an existing spec.md to declare Deltas against and a dedicated changes directory to hold the proposed modification documents.

What is the best way to apply a Delta back into a module spec after approval?

The best way to apply a Delta back into a module spec is through archiving. Upon approval, the archiving step automatically merges the declared Delta from the change document back into the living spec.

Can I use this change management workflow for both new features and refactoring existing modules?

Yes, the template-driven workflow supports bootstrap, feature, enhancement, and refactor workflows. It applies to existing modules by detailing TODO items and declaring Deltas for any type of incremental evolution.