architecture

Define architecture decisions, ownership, contracts, and rollout plans in ADR-ready format.

108|27|Updated Mar 26, 2026

Search Tags:#design #architecture #adr #rollout #system-design #boundary #tradeoffs

Ready to run

npx skills add https://github.com/diegosouzapw/omni-skills --skill architecture-diegosouzapw

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/diegosouzapw/omni-skills/tree/main/skills/architecture
Command: npx skills add https://github.com/diegosouzapw/omni-skills --skill architecture-diegosouzapw

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Defensible architecture decisions prevent drift by clarifying ownership, contracts, and rollout plans for complex systems. This skill helps teams reason about boundaries, sequencing, and tradeoffs to support safe, maintainable changes.

Core Features & Use Cases

Define clear ownership, canonical contracts, and data boundaries for subsystems.
Plan safe migrations with staged rollout and ADR-style rationale.
Provide practical templates and artifacts you can reuse across projects.

Quick Start

Draft an architecture plan outlining boundaries, contracts, and a phased rollout for a given subsystem.

Frequently Asked Questions about architecture

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

FAQPage Schema

How do I document architecture tradeoffs for a system migration?▼

To document architecture tradeoffs, you identify defensible decisions by defining goals, ownership boundaries, canonical contracts, and data flow. This produces an ADR-ready rationale ensuring safe, maintainable changes during migrations.

What is the best way to define ownership and canonical contracts for a subsystem refactor?▼

The best way to define ownership and canonical contracts is to outline clear data boundaries and sequence the rollout. Establishing defensible architecture decisions prevents drift and supports maintainable refactors.

How do I create a phased rollout plan for a new subsystem?▼

You create a phased rollout plan by reasoning through boundaries, sequencing, and tradeoffs. This yields a structured architecture plan defining goals, ownership, and staged rollout steps for safe implementation.

When do I need to write an ADR for system design changes?▼

You need an ADR when designing new subsystems, refactors, or migrations requiring clear ownership and contracts. It captures defensible architecture decisions and tradeoffs to prevent system drift.

Can I use this approach for both new system design and complex refactors?▼

Yes, you can use this architecture approach for both new system design and complex refactors. It applies to any system change where you identify defensible decisions, define boundaries, and establish canonical contracts.