up-elaboration

Guide the Elaboration phase to refine vision, stabilize architecture, and coordinate risk-driven iterations.

Updated Aug 27, 2026

Search Tags:#architecture #open-spec #domain-model #elaboration #system-sequence-diagram #operation-contracts #sw-architecture-document

Ready to run

npx skills add https://github.com/js-rom/Luis --skill up-elaboration

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: up-elaboration
Source: https://github.com/js-rom/Luis/tree/main/.agents/skills/up-elaboration
Command: npx skills add https://github.com/js-rom/Luis --skill up-elaboration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Elaboration phase provides a structured path to refine the project vision, stabilize the core architecture, and establish a credible plan for requirements, architecture, and resources.

Core Features & Use Cases

Coordinate Elaboration activities to refine the project vision, identify high-risk areas, and validate the architectural direction.
Produce core artifacts such as Domain Model, System Sequence Diagrams, Operation Contracts, and a SW Architecture Document to support informed decision-making and planning.
Align the team with an iterative schedule and resource estimates, enabling early feedback and risk mitigation.

Quick Start

Initiate an elaboration cycle by outlining the targeted UCs, sketching the domain model, and drafting an initial architecture outline for the current iteration.

Frequently Asked Questions about up-elaboration

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

FAQPage Schema

What is the elaboration phase in software architecture and when do I need it?▼

The elaboration phase refines the project vision, stabilizes core architecture, and coordinates risk-driven iterations. You need it to identify high-risk areas early and validate architectural direction before committing to full development schedules.

How do I create a domain model and system sequence diagrams for my project?▼

To create a domain model and system sequence diagrams, initiate an elaboration cycle by outlining targeted use cases, sketching the domain model, and drafting an initial architecture outline to support iterative requirements identification and planning.

How do I plan iterative schedules and resource estimates for software development?▼

Plan iterative schedules and resource estimates by applying iterative domain modeling, system sequence diagrams, and operation contracts to identify requirements, enabling early feedback and risk mitigation for realistic project timelines.

How does OpenSpec schema compliance work for architecture documentation?▼

OpenSpec schema compliance ensures artifact freshness and traceability across elaboration steps by validating that domain models, system sequence diagrams, and operation contracts meet defined structural requirements throughout the documentation process.

Can I use operation contracts to identify high-risk areas in my software project?▼

Yes, operation contracts help identify high-risk areas by defining preconditions and postconditions for system operations, enabling teams to validate architectural direction and coordinate risk-driven iterations during the elaboration phase.

What's the difference between elaboration and initial project planning?▼

Elaboration differs from initial planning by focusing on refining the vision through iterative domain modeling and architecture validation rather than basic scoping, producing artifacts like operation contracts and a software architecture document for informed decision-making.