skills.rest
SimpleEve
SimpleEveCOMMUNITY
Explore all skills by this author →
GitHub

eo-spec

Transform ambiguous module requirements into a template-driven spec document.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts ambiguous module ideas into a clear, active spec.md which serves as the baseline for all future changes.

Core Features & Use Cases

  • Generates a living, single-source spec at eo-doc/dev/<module-name>/spec.md that evolves through delta changes.
  • Enforces a fixed spec template and explicit scope boundaries to prevent ambiguity during module initialization.
  • Typical use case: when initializing a brand-new module, trigger /eo-module-init to produce the initial spec and align stakeholders.

Quick Start

Trigger the spec workflow by running the /eo-module-init process to generate the initial spec at eo-doc/dev/<module-name>/spec.md.

Frequently Asked Questions about eo-spec

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

FAQPage Schema
How do I turn vague ideas into a clear module spec?▼

To turn vague ideas into a clear module spec, you trigger a template-driven workflow that transforms ambiguous requirements into a structured spec.md document, establishing a solid baseline without assuming implementation details.

What is a living specification document for a new software module?▼

A living specification document is a single-source spec.md file that defines a module's requirements and scope boundaries, serving as an active baseline that evolves through subsequent delta changes.

How do I generate the initial spec for a new module?▼

You generate the initial spec by running the module-init process, which drafts the specification file at eo-doc/dev/<module-name>/spec.md to align stakeholders during module initialization.

Does the module spec include implementation code?▼

No, the module spec strictly avoids code and assumes no implementation details, focusing entirely on delineating in-scope versus out-of-scope requirements using a fixed template structure.

Can I modify an existing module's requirements through the spec workflow?▼

No, you cannot modify existing modules through the spec workflow; the spec document only initializes a baseline for new modules, and all subsequent changes must flow through a dedicated delta change process.

Related Skills

Explore More Software Engineering Skills→
SimpleEveSimpleEve
30

eo-module-init

Create a validated module spec and initial review baseline.

Community
Intermediate
SimpleEveSimpleEve
30

eo-change

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

Community
Intermediate
zerobias-orgzerobias-org

monorepo-structure

Define standard monorepo module layouts with package/{vendor}/{module} paths.

Official
Intermediate
product-on-purposeproduct-on-purpose
527

deliver-prd

Generate structured Product Requirements Documents with problem statements, goals, and requirements.

Official
Intermediate