architectural-analysis

Extract and prioritize FURPS+ architectural factors from Vision and Use Case Model inputs.

Updated Aug 23, 2026

Search Tags:#risk-management #software-architecture #design-decisions #pair-programming #architectural-analysis #FURPS+#factor-tables

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and prioritize architecturally significant concerns early in the design process to reduce risk and improve decision traceability.

Core Features & Use Cases

Factor extraction from Vision, Use Case Model, and Supplementary Specification.
Classification into FURPS+ categories.
Generation of a structured factor table with prioritization and rationale.
Production of Technical Memos with decisions and alternatives.

Use Case: Analysts can review the factor table and memo to inform trade-off discussions with stakeholders and to guide architectural decisions.

Quick Start

Provide Vision, Use Case Model, and Supplementary Specification to begin analysis and generate the factor table with prioritized design decisions.

Frequently Asked Questions about architectural-analysis

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

FAQPage Schema

How do I identify and prioritize architectural factors for software design decisions?▼

To identify and prioritize architectural factors, you analyze Vision, Use Case Model, and Supplementary Specification inputs to extract concerns, classify them into FURPS+ categories, and generate a structured factor table with traceable rationale.

What is a FURPS+ factor table and how does it guide architectural analysis?▼

A FURPS+ factor table is a structured classification of architecturally significant concerns categorized by Functionality, Usability, Reliability, Performance, and Supportability. It guides architectural analysis by prioritizing design decisions with explicit trade-off analysis and traceable rationale.

How do I generate technical memos with design decisions and alternatives for stakeholders?▼

You generate technical memos by processing Vision, Use Case Model, and Supplementary Specification inputs through a pair-programming workflow, producing factor tables that inform trade-off discussions and output explicit decisions with documented alternatives.

What inputs do I need for architectural analysis to reduce early design risks?▼

Architectural analysis requires three inputs: a Vision document, a Use Case Model, and a Supplementary Specification. Providing these allows the workflow to extract and prioritize FURPS+ factors, reducing risk early in the design process.

Can I use pair-programming workflows to trace architectural design rationale?▼

Yes, architectural analysis satisfies a mandatory pair-programming workflow by executing step-by-step analysis, generating factor tables, and producing technical memos with explicit trade-off analysis and traceable rationale for design decisions.

What is the best way to analyze architectural trade-offs for software projects?▼

The best way to analyze architectural trade-offs is extracting FURPS+ factors from project specifications to build a prioritized factor table, enabling structured technical memos that compare alternatives and justify decisions for stakeholder review.