eo-change-review

Review change.md drafts for spec-delta compliance and implementation feasibility.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill ensures that draft change proposals are thoroughly vetted for spec delta correctness, implementation feasibility, and complete TODO lists before moving to the implementation phase.

Core Features & Use Cases

  • Delta Compliance Check: Verifies that added, modified, or removed spec entries align with the current module spec.
  • Implementation Alignment: Confirms that the implementation plan covers all delta items without over‑ or under‑scope.
  • Todo & Acceptance Review: Inspects completeness of TODO items and acceptance criteria, flagging blockers (P0) and suggestions (P1).
  • Use Case: When a developer finishes drafting a change.md, they run this skill to receive a structured change‑review.md report indicating any issues that must be fixed before /eo-implement.

Quick Start

Run the eo-change-review skill on a draft change to obtain a compliance report.

Frequently Asked Questions about eo-change-review

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

FAQPage Schema
How do I validate a draft change document before implementation?

To validate a draft change document, review it for spec delta correctness and implementation feasibility. This process checks that added, modified, or removed spec entries align with the current module spec before moving to the implementation phase.

What is a spec-delta compliance check in software workflows?

A spec-delta compliance check verifies that added, modified, or removed specification entries align with the current module spec. It ensures draft change proposals accurately reflect intended modifications before implementation begins.

How do I ensure my implementation plan covers all change items without scope creep?

Ensure your implementation plan covers all change items by performing an implementation alignment check. This confirms the plan covers all delta items without over- or under-scoping, preventing scope creep during the software development workflow.

When do I need to run a change review on my development workflow?

You need to run a change review during the pre-implement stage after drafting a change.md file. It produces a change-review.md report highlighting P0 issues and P1 suggestions that must be fixed before implementation.

Does the change review process flag incomplete TODO items and acceptance criteria?

Yes, the change review process inspects the completeness of TODO items and acceptance criteria. It actively flags blockers as P0 issues and suggestions as P1 issues within the generated change-review.md report.

What is the best way to identify P0 blockers in a change proposal?

The best way to identify P0 blockers in a change proposal is to inspect TODO items and acceptance criteria for completeness. This review generates a structured report highlighting P0 issues that must be fixed before implementation.