east-design

Architect business-oriented software solutions using East and e3 frameworks.

Updated Nov 10, 2025
One-click install
npx skills add https://github.com/elaraai/east-workspace --skill east-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: east-design
Source: https://github.com/elaraai/east-workspace/tree/main/libs/east-claude-plugin/skills/east-design
Command: npx skills add https://github.com/elaraai/east-workspace --skill east-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents common architectural failures by forcing a decision-first design process, ensuring that technical implementations are grounded in business value rather than just data movement.

Core Features & Use Cases

  • Decision-First Discovery: Maps business goals to specific economic ontologies and decision surfaces.
  • Stack Alignment: Guides the selection of appropriate East packages (e3, east-ontology, east-py-datascience) based on the required data flow and runtime needs.
  • Design Documentation: Generates a structured architecture document that defines the decision, evidence, data flow, and required components before any code is written.

Quick Start

Use the east-design skill to architect a new solution for optimizing inventory replenishment based on historical sales data.

Frequently Asked Questions about east-design

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

FAQPage Schema
How do I map business objectives to a decision pipeline architecture?

Designing decision-oriented architecture requires mapping business goals to economic ontologies and decision surfaces. This skill validates requirements for data integration and computational reasoning before generating structured architecture documents.

How do I document data flow and technical components before writing code?

Documenting data flow and required components involves generating a structured architecture document. This defines the decision, evidence, and data flow before any code is written to prevent common architectural failures.

Can I use the East framework to validate data integration requirements?

The East framework validates architectural requirements for data integration, computational reasoning, and interactive decision surfaces. It ensures technical implementations are grounded in business value rather than just data movement.

What is the best way to architect a decision-first software solution?

Architecting a decision-first solution requires mapping business goals to economic ontologies and decision surfaces. This prevents common architectural failures by grounding technical implementations in business value rather than data movement.

Does this approach guide the selection of East packages like east-ontology?

Stack alignment guides the selection of appropriate East packages, including east-ontology, e3, and east-py-datascience. Package selection is based on the required data flow and runtime needs of the decision pipeline.

When should I avoid decision-first architectural design?

Decision-first architectural design should be avoided when a project only requires simple data movement without complex computational reasoning or interactive decision surfaces. This approach specifically targets data-driven pipelines mapping business objectives to technical execution models.