eiffel-spec

Convert research outputs into formal Eiffel specifications with domain models and contracts.

Updated Jan 22, 2026
One-click install
npx skills add https://github.com/simple-eiffel/eiffel-spec-kit --skill eiffel-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eiffel-spec
Source: https://github.com/simple-eiffel/eiffel-spec-kit/tree/main/eiffel-spec
Command: npx skills add https://github.com/simple-eiffel/eiffel-spec-kit --skill eiffel-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts research outputs into a formal Eiffel specification, establishing a solid design foundation and an auditable blueprint for downstream phases.

Core Features & Use Cases

  • Research-to-spec transformation: converts inputs from /eiffel.research into a structured spec under .eiffel-workflow/spec.
  • OOSC2-aligned design artifacts: yields domain models, class designs, contracts, interfaces, and a complete specification set.
  • Workflow guidance: documents prerequisites and steps to move from analysis to validation, ensuring traceability.

Quick Start

Run the pre-phase spec workflow against your project path, ensuring research outputs exist at <project>/.eiffel-workflow/research and inspect generated files under <project>/.eiffel-workflow/spec.

Frequently Asked Questions about eiffel-spec

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

FAQPage Schema
How do I convert domain research results into formal Eiffel specifications?

To convert domain research results into formal Eiffel specifications, run the pre-phase spec workflow against your project path to generate structured OOSC2-aligned artifacts under the .eiffel-workflow/spec directory.

What is design-by-contract and how does it apply to domain modeling?

Design-by-contract applies to domain modeling by establishing formal specifications with precise interfaces and contracts. This skill generates class designs and domain models that enforce preconditions, postconditions, and invariants for downstream development.

Can I generate class designs and interfaces from existing research outputs?

Yes, you can generate class designs and interfaces from existing research outputs by ensuring inputs exist at .eiffel-workflow/research. The workflow processes these inputs to produce a complete OOSC2-aligned specification set for your project.

What's the best way to structure specification documents for pre-intent design phases?

The best way to structure specification documents is using the .eiffel-workflow/spec directory, which organizes outputs sequentially from 01-parsing requirements through 08-validation, documenting decisions and ensuring traceability for downstream phases.

Do I need prior research artifacts to start generating Eiffel specifications?

Yes, you need prior research artifacts located at <project>/.eiffel-workflow/research to start generating Eiffel specifications. The workflow targets post-research to pre-intent transitions and requires these inputs to produce domain models and contracts.

Why does my research-to-spec transition lack traceability for downstream design?

Your research-to-spec transition lacks traceability because decision documentation is missing. This skill ensures traceability by documenting prerequisites and workflow steps, moving from analysis to validation while producing an auditable blueprint.