eo-module-init

Create a validated module spec and initial review baseline.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

A new module needs a standardized, reviewable specification and repository skeleton before any implementation can begin; manual setup is error-prone and inconsistent across projects. This Skill automates the creation of a live spec, enforces a first spec-review, and prepares the changes timeline so future work follows the repository's eo-change workflow.

Core Features & Use Cases

  • Automated spec creation: Produces eo-doc/dev/<module-name>/spec.md using the eo-spec template and initial content tailored to the module.
  • Mandatory initial review: Runs a spec-review process and requires resolution of P0/P1 findings before the module baseline is accepted.
  • Repository skeleton: Creates changes/ and a module-level INDEX.md and updates the global eo-doc/dev/INDEX.md so the module is discoverable.
  • Use case: When introducing a new domain module like inventory or transport-queue, run this Skill to establish a confirmed spec and ready the project for bootstrap changes.

Quick Start

Initialize a new module named inventory, generate eo-doc/dev/inventory/spec.md, confirm the spec status, run the spec-review until passing, create the changes/ skeleton with INDEX.md, and update the global dev index.

Frequently Asked Questions about eo-module-init

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

FAQPage Schema
How do I bootstrap a new module spec and repository skeleton?

To bootstrap a module spec, you generate a validated spec.md, enforce an initial spec-review baseline, create a changes/ skeleton with INDEX.md, and update the global module index for discoverability.

Why do I need an initial spec-review before starting module implementation?

An initial spec-review is required to resolve P0/P1 findings before the module baseline is accepted, ensuring the specification is validated and consistent before implementation begins.

What format should the module name be when creating a new code module?

The module name must be in kebab-case format. The initialization process verifies this naming convention and checks for directory conflicts before creating the eo-doc/dev/<module-name>/ structure.

Can I use this module initialization workflow if the eo-doc/dev directory already exists?

No, this module initialization workflow applies when the eo-doc/dev/<module-name>/ directory does not exist and the user needs a confirmed spec baseline for a brand-new code module.

How does automated spec creation handle the changes timeline for future work?

Automated spec creation prepares a changes/ skeleton with an INDEX.md, establishing a repository structure so future modifications follow the repository's eo-change workflow seamlessly.