software-engineering-eng-architect

Designs evolutionary software architectures using fitness functions and evidence-first analysis.

Updated May 6, 2025
One-click install
npx skills add https://github.com/rodrigo-altissimo/qiartificial --skill software-engineering-eng-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: software-engineering-eng-architect
Source: https://github.com/rodrigo-altissimo/qiartificial/tree/main/.claude/skills/software-engineering/eng-architect
Command: npx skills add https://github.com/rodrigo-altissimo/qiartificial --skill software-engineering-eng-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of making risky software architecture decisions without measurable goals, evidence, or clear trade-offs—especially when requirements evolve and coupling costs accumulate over time.

Core Features & Use Cases

  • Evolutionary architecture guidance: Produces architecture recommendations driven by explicit architectural fitness functions rather than opinions.
  • Coupling- and evidence-first evaluation: Guides discovery with a minimum viable evidence checklist (team size, deployment frequency, prioritized -ilities, current architecture, domain complexity, operational maturity) and requests only what is missing.
  • Decision support and documentation: Maps requests to tasks like architecture design, coupling evaluation, trade-off analysis, ADR creation, design reviews, and migration strategies (strangler fig).
  • Use cases: Greenfield system design, brownfield architecture assessment and migration planning, and decision-time trade-off discussions (e.g., monolith vs microservices, event-driven, ADRs).

Quick Start

Ask the AI to design an evolvable architecture for your system by stating your team size, deployment frequency, and the top architectural concerns you want to optimize.

Frequently Asked Questions about software-engineering-eng-architect

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

FAQPage Schema
How do I design an evolvable software architecture using fitness functions?

Evolvable architecture design uses fitness functions to continuously measure and enforce key architectural -ilities, ensuring your system adapts measurably as requirements evolve rather than relying on opinion-based design choices.

What is the minimum evidence needed for a coupling analysis and architecture evaluation?

Coupling analysis requires minimum viable evidence including team size, deployment frequency, prioritized -ilities, current architecture state, domain complexity, and operational maturity to perform evidence-first architectural evaluation.

How do I create an Architecture Decision Record for a monolith vs microservices trade-off?

Create an Architecture Decision Record by mapping your monolith vs microservices trade-off discussion through explicit trade-off analysis, capturing context, decision drivers, and evaluated alternatives to formalize the architectural choice.

What is the best way to plan a migration strategy from a monolith to an evolvable architecture?

Plan migration strategy using the strangler fig pattern to incrementally replace monolith components, evaluating coupling costs and architectural fitness functions to ensure the new architecture meets your prioritized -ilities.

When should I not use microservices for a greenfield architecture design?

Avoid microservices in greenfield architecture design when your team size, deployment frequency, or operational maturity cannot support distributed system overhead, as evidence-first evaluation may favor a monolith based on your prioritized -ilities.