architecture

Evaluate design options and document architectural decisions as ADRs.

2|1|Updated Nov 7, 2025
One-click install
npx skills add https://github.com/is-ivanov/rpm-ddd --skill architecture-is-ivanov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/is-ivanov/rpm-ddd/tree/main/.opencode/skills/architecture
Command: npx skills add https://github.com/is-ivanov/rpm-ddd --skill architecture-is-ivanov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps when implementation reaches an architectural fork and several reasonable designs are possible. It creates a structured way to pause, compare options, capture trade-offs, and document the decision before more code is written.

Core Features & Use Cases

  • Decision Framing: Clarifies the exact architectural question, constraints, and trigger behind the decision.
  • Option Analysis: Guides comparison of 2-4 approaches for issues like schema design, processing strategy, race condition handling, and domain modeling.
  • ADR Creation and Follow-Through: Produces a concise architectural decision record, updates test specifications with newly discovered edge cases, and records implementation steps in project progress notes.
  • Use Case: When a team is unsure how to order tasks within workflow columns or how to model concurrent updates safely, this Skill supports discussion, trade-off review, and formal documentation before implementation continues.

Quick Start

Ask the architecture skill to evaluate a specific design decision for your current story and document the chosen approach as an ADR.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I evaluate architectural design options before coding?

To evaluate architectural design options before coding, frame the exact decision question and constraints, compare 2-4 viable approaches, and capture trade-offs in an architectural decision record to formalize the chosen path.

What is an architectural decision record and when do I need one?

An architectural decision record is a concise document that captures design trade-offs and the rationale behind a chosen approach. You need one when implementation reaches an architectural fork with multiple reasonable designs.

How do I handle race conditions and domain modeling during schema design?

Handling race conditions and domain modeling during schema design requires comparing processing strategies for concurrent updates, evaluating trade-offs, and documenting the selected approach to ensure safe implementation.

Can I plan TDD implementation steps while making design decisions?

Yes, you can plan TDD implementation steps while making design decisions by updating test specifications with newly discovered edge cases and recording the implementation steps in project progress notes alongside the ADR.

What is the best way to document software architecture trade-offs?

The best way to document software architecture trade-offs is creating an architectural decision record that clarifies the decision question, compares viable options, and captures the rationale before continuing implementation.