software-architecture-engineering-uap

Name: software-architecture-engineering-uap
Availability: InStock
Author: Oghie

Document software architecture decisions with ADRs and traceable evidence.

8|Updated Jun 17, 2026

Search Tags:#design #architecture #adr #verification #governance #rfc #nfr

Ready to run

npx skills add https://github.com/oghie/skillsets --skill software-architecture-engineering-uap

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: software-architecture-engineering-uap
Source: https://github.com/oghie/skillsets/tree/main/software_architecture_skill
Command: npx skills add https://github.com/oghie/skillsets --skill software-architecture-engineering-uap

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires yaml, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill delivers disciplined architecture decisions that replace guesswork with traceable, evidence-based reasoning for software systems.

Core Features & Use Cases

Unified Architecture Process (A0-A6) coverage for requirements, context, schematic design, views, and evaluation.
Production of architecture artifacts, ADRs/RFCs, diagrams, and fitness/conformance artifacts.
NFR conformance, cost-aware decisions, and architecture-as-code governance integrated with development and operation needs.
Security pattern design, IAM/auth considerations, and auditability across functional, information, and deployment views.
Support for modernization, decomposition, and architecture evolution with verification planning and rollout readiness.

Quick Start

Define scope and inputs, then apply the Unified Architecture Process to generate plans, views, and verifications.

Frequently Asked Questions about software-architecture-engineering-uap

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

FAQPage Schema

How do I document software architecture decisions with traceable evidence?▼

Generate ADRs and RFCs that replace guesswork with traceable evidence, explicit boundaries, and verifiable tests. This approach enforces architecture governance through views, fitness functions, and conformance maps across your software systems.

What is the Unified Architecture Process for software systems?▼

The Unified Architecture Process is a structured workflow covering phases A0 through A6 for requirements, context, schematic design, views, and evaluation. It delivers disciplined architecture decisions across greenfield and legacy software systems.

How do I ensure NFR conformance and architecture-as-code governance?▼

Ensure NFR conformance and architecture-as-code governance by integrating cost-aware decisions with development and operation needs. Generate fitness and conformance artifacts that verify security patterns, IAM considerations, and auditability across functional views.

Can I use this for legacy system modernization and decomposition?▼

Yes, you can use this for legacy system modernization and decomposition. It supports architecture evolution with verification planning and rollout readiness, producing verifiable tests and conformance maps for both greenfield and legacy software systems.

What's the best way to evaluate architecture views and fitness functions?▼

Evaluate architecture views and fitness functions by applying the Unified Architecture Process to generate plans, views, and verifications. This method requires explicit boundaries and domain references to produce verifiable conformance maps.