spec-morphisms

Extract categorical morphisms from natural language requirements into morphisms.yaml.

37|5|Updated Nov 18, 2025

Search Tags:#domain modeling #morphisms #requirements extraction

Ready to run

npx skills add https://github.com/BellaBe/lean-os --skill spec-morphisms

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-morphisms
Source: https://github.com/BellaBe/lean-os/tree/main/.claude/skills/spec-morphisms
Command: npx skills add https://github.com/BellaBe/lean-os --skill spec-morphisms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies categorical morphisms from natural language requirements, detailing domain, codomain, effects, and composition type.

Core Features & Use Cases

Morphism extraction: identify domain, codomain, and effects.
Composition classification: distinguish pure vs. Kleisli morphisms and composed morphisms.
Output: artifacts/v{N}/spec/morphisms.yaml.

Quick Start

Example: "Extract morphisms from requirements into artifacts/v1/spec/morphisms.yaml."

Frequently Asked Questions about spec-morphisms

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

FAQPage Schema

How do I extract morphisms from natural language requirements?▼

Morphism extraction identifies domain, codomain, and effects from requirements text. This Skill analyzes natural language requirements and artifacts to classify operations as pure or Kleisli morphisms, marking them as generators or derived from composition, outputting results to artifacts/v{N}/spec/morphisms.yaml for traceability.

What's the difference between generator and derived morphisms in domain modeling?▼

Generator morphisms are primitive operations extracted directly from requirements; derived morphisms result from composing generators. This Skill distinguishes both types and documents composition relations, enabling you to trace which morphisms are foundational versus built from existing operations.

Can I use morphism extraction to model domain operations from requirements documents?▼

Yes. Morphism extraction applies categorical reasoning to requirements, identifying domain and codomain for each operation and classifying effects. The output YAML file documents each morphism's type, composition chain, and textual description, creating a formal model of your domain's operations.

How do pure and Kleisli morphisms differ in requirements analysis?▼

Pure morphisms have no side effects; Kleisli morphisms encode effects like I/O or failure. This Skill classifies each extracted morphism by composition type, helping you distinguish operations by their effectful behavior so domain models accurately reflect system constraints.

What output does morphism extraction produce?▼

The Skill produces artifacts/v{N}/spec/morphisms.yaml containing morphism definitions with generator/derived flags, composition relations, domain and codomain types, effect classifications, and textual descriptions linking each morphism back to requirements.