architecture

Identify and articulate architecture decisions across compute, databases, storage, networking, messaging, observability, and cost.

3|Updated Apr 12, 2026

Search Tags:#architecture #governance #cloud #infrastructure-as-code #deployments #architecture-decisions #compute

Ready to run

npx skills add https://github.com/mauriciodelrio/delriodev-skills --skill architecture-mauriciodelrio

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/mauriciodelrio/delriodev-skills/tree/main/es-skills/software/architecture
Command: npx skills add https://github.com/mauriciodelrio/delriodev-skills --skill architecture-mauriciodelrio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides teams to design and document architectures for software projects, ensuring decisions are justified, traceable, and technology-agnostic.

Core Features & Use Cases

Discovery-driven decision framework covering compute, databases, storage, networking, messaging, observability, and cost.
End-to-end workflow from discovery to implementation, with sub-skills orchestration and situational guidance.
Suitable for projects of any scale, from MVPs to large platforms, where technology choices must be justified rather than assumed.

Quick Start

Provide project context and constraints to generate an architecture decision framework.

Frequently Asked Questions about architecture

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

FAQPage Schema

How do I document architecture decisions for compute, storage, and networking across projects?▼

Document architecture decisions by applying a technology-agnostic framework that identifies and articulates choices across compute, storage, networking, and cost. This ensures decisions are traceable, justified, and aligned with business goals and risk tolerance.

Can I use this architecture decision framework for both MVPs and large platforms?▼

Yes, the architecture decision framework is suitable for projects of any scale, from MVPs to large platforms. It provides situational guidance and sub-skills orchestration to justify technology choices rather than assuming them.

What's the best way to ensure architecture decisions are aligned with business constraints?▼

The best way to align architecture decisions with business constraints is using a discovery-driven framework. It guides analysis and proposal workflows to ensure every compute, database, and messaging choice is justified and traceable.

How does a technology-agnostic architecture decision framework work?▼

A technology-agnostic architecture decision framework works through a discovery workflow that analyzes constraints across observability, messaging, and infrastructure. It structures proposals to ensure decisions are justified without locking into specific tools.

Do I need to provide project context to generate an architecture decision framework?▼

Yes, you need to provide project context and constraints to generate an architecture decision framework. The tool uses this input to apply its discovery-driven analysis across compute, databases, networking, and cost domains.

When should I use a structured architecture decision process instead of choosing tools directly?▼

Use a structured architecture decision process when technology choices must be justified rather than assumed. It ensures decisions across compute, messaging, and observability are traceable and aligned with risk tolerance and business goals.