architectural-design

Automate architecture decisions for software projects with dependency rules and evolution plans.

Updated Aug 23, 2026

Search Tags:#architecture #modularity #system-architecture #design-decision #quality-attributes #dependency-governance

Ready to run

npx skills add https://github.com/js-rom/Luis --skill architectural-design-js-rom

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables architecture-level decision making and documentation to guide system design, governance, and evolution across packages, components, and deployment constraints.

Core Features & Use Cases

Architecture drivers and context definition for project scope.
Evaluation of candidate styles and selection of a baseline or hybrid approach.
Definition of package governance: dependencies, cohesion, and quality attribute tactics.
Risk, trade-off, and evolution planning with traceability to use cases and requirements.

Quick Start

Define architecture drivers and produce an evolution plan for the current iteration.

Frequently Asked Questions about architectural-design

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

FAQPage Schema

How do I define software architecture drivers for a new project?▼

Software architecture drivers are defined by establishing the project context and scope to guide system-level design. This skill automates capturing these drivers to produce a baseline for package governance and quality attribute planning.

What is the best way to document system architecture trade-offs and evolution plans?▼

Documenting system architecture trade-offs requires mapping risks and quality attribute tactics to use cases. This skill automates generating an evolution plan with traceability to requirements and dependency rules.

How to evaluate candidate architecture styles for a software system?▼

Evaluating architecture styles involves comparing candidate approaches against defined project drivers. This skill automates the evaluation process to select a baseline or hybrid style for your system design.

Can I use this for package governance and dependency rules across multiple components?▼

Yes, package governance is supported by defining dependencies, cohesion, and quality attribute tactics. The skill applies these dependency rules across multiple components for system-level design.

What is included in quality attribute planning for software architecture?▼

Quality attribute planning involves defining specific tactics to meet system requirements like modularity. This skill automates integrating these attributes into your architecture decisions and package governance.