architecture

Document architectural decisions with trade-offs using ADR templates.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/datamonsterr/justplan --skill architecture-datamonsterr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/datamonsterr/justplan/tree/main/.github/skills/architecture
Command: npx skills add https://github.com/datamonsterr/justplan --skill architecture-datamonsterr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architectural decisions are often inconsistent and hard to justify. This framework provides a structured approach to capture requirements, evaluate trade-offs, and document decisions as ADRs, ensuring traceability and shared understanding across teams.

Core Features & Use Cases

  • ADR templates & references for consistent decision records
  • Trade-off analysis to capture rationale and impacts
  • Context discovery prompts to frame design questions upfront
  • Pattern references and linked guidance to accelerate decisions

Quick Start

Create an ADR for a design decision by outlining context, options, decision, and consequences using the framework

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I document architectural decisions to ensure traceability across teams?▼

Document architectural decisions using ADR templates to capture context, options, and consequences. This structured approach ensures traceability and shared understanding across teams by recording trade-offs and rationale.

What is an ADR and when do I need to write one for software design?▼

An ADR is an Architectural Decision Record used to document design choices and trade-offs. You need to write one when evaluating architecture decisions to capture rationale, impacts, and context for future reference.

How do I frame design questions before making an architecture trade-off analysis?▼

Use context discovery prompts to frame design questions upfront before conducting trade-off analysis. This captures requirements and evaluates impacts to guide consistent architectural decisions.

What is the best way to structure an ADR for a new design decision?▼

The best way to structure an ADR is outlining context, options, decision, and consequences. Using ADR templates and pattern references ensures consistent decision records and accelerates the process.

Can I use ADR documentation for projects requiring trade-off analysis across multiple teams?▼

Yes, ADR documentation supports projects requiring architecture decisions, trade-off analysis, and context discovery across teams. It provides linked guidance and pattern references to accelerate decisions.

Why does my team struggle to justify architectural decisions consistently?▼

Architectural decisions are often inconsistent without a structured framework. Using ADR templates with context discovery and trade-off analysis ensures decisions are documented with clear rationale and traceable impacts.