metodologia-ai-software-architecture

Define module boundaries and document ADRs for AI-enabled systems.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/JaviMontano/metodologia-propuesta-agent-public --skill metodologia-ai-software-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: metodologia-ai-software-architecture
Source: https://github.com/JaviMontano/metodologia-propuesta-agent-public/tree/main/.claude/skills/ai/ai-software-architecture
Command: npx skills add https://github.com/JaviMontano/metodologia-propuesta-agent-public --skill metodologia-ai-software-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides a structured framework to design and document AI-enabled software architectures, ensuring consistent module boundaries, layer separation, decision records, and governance to manage AI-specific debt.

Core Features & Use Cases

  • Defines a scalable, six-layer AI architecture (Hardware, Data, Model, Inference, Application, Monitoring & Control) and guidance on when to apply ADRs and quality attributes.
  • Produces Architecture Decision Records (ADRs), debt evolution plans, and evaluation criteria to support cross-functional teams (data, model, and software engineers).
  • Useful for planning new AI systems, refactoring existing AI pipelines, and aligning architecture with governance and regulatory needs (drift, explainability, fairness).

Quick Start

Draft a concise AI architecture plan outlining modules, layers, ADRs, and quality attributes for an AI-enabled service.

Frequently Asked Questions about metodologia-ai-software-architecture

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

FAQPage Schema
How do I document AI system architecture decisions for ML pipelines?

Document AI system architecture decisions by generating Architecture Decision Records (ADRs) that capture module boundaries, layer separation, and debt evolution plans across hardware, data, model, and inference layers.

What is the best way to structure an AI-enabled software architecture?

Structure AI-enabled software architecture using a six-layer model: Hardware, Data, Model, Inference, Application, and Monitoring & Control. This defines scalable module boundaries and quality attributes for cross-functional teams.

How do I manage AI-specific technical debt when refactoring AI pipelines?

Manage AI-specific technical debt by creating a debt evolution plan that tracks architecture decisions and monitors quality attributes like drift, explainability, and fairness throughout the ML pipeline lifecycle.

When do I need Architecture Decision Records for software design?

You need Architecture Decision Records when defining module boundaries, selecting architecture patterns, or evaluating ML pipeline architecture to ensure governance and align with regulatory needs like drift detection.

Can I use this framework to align AI architecture with governance and regulatory needs?

Yes, this framework aligns AI architecture with governance by evaluating quality attributes such as drift detection, explainability, and fairness, ensuring regulatory compliance across data, model, and application layers.

What quality attributes should I evaluate for AI pipeline architecture?

Evaluate quality attributes for AI pipeline architecture including drift detection, explainability, and fairness. These attributes ensure proper governance across the six architectural layers from data to monitoring.