eo-implement

Name: eo-implement
Availability: InStock
Author: SimpleEve

Execute TODOs from change.md to implement code and validate with tests.

30|5|Updated Apr 5, 2026

Search Tags:#workflow #testing #implement #code-generation #bug-fix #change-management

Ready to run

npx skills add https://github.com/SimpleEve/eo-skills --skill eo-implement

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: eo-implement
Source: https://github.com/SimpleEve/eo-skills/tree/main/eo-implement
Command: npx skills add https://github.com/SimpleEve/eo-skills --skill eo-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translates change plans into working code by executing the TODOs defined in change.md and applying fixes within the change lifecycle.

Core Features & Use Cases

Aligns implementation work with the change lifecycle, ensuring TODOs are followed and traceable.
Applies the change plan to codebase, validates through test and review stages, and records deviations only when necessary.
Supports layered workflows: first implement, then test and review, with clear status transitions and delta tracking.

Quick Start

Provide the implement plan from change.md and begin coding to fulfill all TODO items, then run tests and seek review.

Frequently Asked Questions about eo-implement

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

FAQPage Schema

How do I turn a change plan into working code automatically?▼

To turn a change plan into working code, you provide the implementation plan from a change.md file and the system executes the defined TODOs to generate code, apply fixes, and validate with tests.

What is a delta-based workflow for implementing code changes?▼

A delta-based workflow for implementing code changes enforces strict adherence to a change lifecycle, ensuring traceability from specification to implementation by tracking only the modifications applied to the baseline spec.md.

How do I implement features and fix bugs using a change lifecycle?▼

You implement features and fix bugs within a change lifecycle by applying a change plan to the codebase, transitioning through layered statuses to implement, test, and review the generated code.

Can I record deviations when applying code generation to an existing baseline?▼

Yes, you can record deviations when applying code generation to an existing baseline, but deviations are documented only when necessary during the test and review stages of the change lifecycle.

Does the code implementation workflow require a spec.md baseline file?▼

Yes, the code implementation workflow requires a spec.md baseline file to ensure compliance, maintain traceability from spec to implementation, and validate the applied changes against the original module requirements.

Why are my TODO items from change.md not executing during implementation?▼

TODO items from change.md may not execute if the implementation workflow detects non-compliance with the spec.md baseline or if the layered status transitions for testing and review are not properly followed.