architecture

Provide a structured ADR framework for architecture decisions.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/AnvinX1/med-rag --skill architecture-anvinx1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/AnvinX1/med-rag/tree/main/medical_genai_app/.agent/skills/architecture
Command: npx skills add https://github.com/AnvinX1/med-rag --skill architecture-anvinx1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architectural decision-making framework to analyze requirements, evaluate trade-offs, and capture ADRs to guide design choices.

Core Features & Use Cases

  • Requirements analysis, trade-off evaluation, and ADR documentation
  • Guidance for selecting architecture patterns and documenting decisions
  • Use during architecture reviews to align stakeholders and justify design choices

Quick Start

Propose and record an ADR for your current architecture decision by drafting context, options, rationale, and outcome.

Frequently Asked Questions about architecture

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

FAQPage Schema
What is an ADR and when do I need to document architecture decisions?

An ADR (Architecture Decision Record) captures context, options, rationale, and outcomes for design choices. You need ADR documentation when evaluating trade-offs or conducting architecture reviews to align stakeholders on software projects.

How do I write an ADR for a software architecture trade-off evaluation?

To write an ADR for architecture trade-off evaluation, draft the context, list available options, provide rationale for the chosen design, and define the expected outcome. This structured framework guides pattern selection and justifies your decision.

What's the best way to structure architecture reviews to align stakeholders?

The best way to structure architecture reviews is using an ADR-driven framework that explicitly documents requirements, evaluates trade-offs, and records design rationales to align stakeholders and justify specific architecture patterns.

Does this ADR framework require any specific documentation tools or dependencies?

No specific tools or dependencies are required. The framework supplies templates and guidance for ADR documentation directly, requiring only that your SKILL.md includes standard YAML frontmatter for name and description metadata.

Can I use ADR documentation for requirements analysis before choosing architecture patterns?

Yes, you can use ADR documentation during requirements analysis. The framework helps analyze requirements, evaluate trade-offs, and capture decision records before selecting architecture patterns, ensuring design choices are justified.

Why should I not use informal documentation instead of structured ADRs for architecture decisions?

Informal documentation lacks the structured context, trade-off evaluation, and rationale needed for effective architecture reviews. Structured ADRs ensure decision-making is explicit, traceable, and aligns stakeholders across software projects.