skills.rest
PoyoPoak
PoyoPoakCOMMUNITY
Explore all skills by this author →
GitHub

architecture

Document architecture decisions by comparing technologies and capturing trade-offs.

Updated Aug 27, 2026
Search Tags:#architecture#documentation#adr#trade-offs#system-design#design-decision
One-click install
npx skills add https://github.com/PoyoPoak/FastAPI-App-Template --skill architecture-poyopoak
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/PoyoPoak/FastAPI-App-Template/tree/main/.agents/skills/architecture
Command: npx skills add https://github.com/PoyoPoak/FastAPI-App-Template --skill architecture-poyopoak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.

Core Features & Use Cases

  • Create an Architecture Decision Record (ADR) to document decision context, options considered, trade-offs, and consequences.
  • Evaluate a system design proposal by comparing alternatives and capturing rationale.
  • Reuse ADRs to guide implementation choices and future maintenance across projects.

Quick Start

Create an ADR for a Kafka vs SQS decision and capture context, options, and next steps.

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 and capture trade-offs for system design proposals?▼

Documenting architecture decisions involves creating an Architecture Decision Record (ADR) to capture context, alternatives, criteria, and consequences. It applies structured templates to evaluate system designs across requirements and constraints in software projects.

What is an ADR and when do I need it for evaluating technologies like Kafka vs SQS?▼

An ADR, or Architecture Decision Record, is a structured document used when choosing between technologies like Kafka and SQS. You need it to formally record design decisions, evaluate alternatives, and capture the rationale behind trade-offs and consequences.

Can I evaluate a system design proposal by comparing alternatives within this workflow?▼

Evaluating a system design proposal requires comparing alternatives and capturing rationale to guide implementation choices. You can apply a structured ADR template to record context, options, and sign-off workflows for future maintenance across projects.

What's the best way to structure trade-off analysis when designing a new component from requirements?▼

The best way to structure trade-off analysis is using an ADR template that records context, alternatives, criteria, and consequences. This ensures all design decisions are evaluated against project requirements and constraints before final sign-off.

Does this approach work for reusing past architecture decisions to guide future maintenance across projects?▼

Reusing ADRs works effectively to guide implementation choices and future maintenance across projects. By capturing decision context, options considered, and consequences, teams maintain a structured record of rationale for ongoing system design evaluation.

Related Skills

Explore More Software Engineering Skills→
jagreehaljagreehal
3

system-architecture

Document architecture decisions and trade-offs using ADR patterns.

Community
Basic
Marwan78888Marwan78888
16

architecture-designer

Design scalable system architectures and document decisions with ADRs.

Community
Advanced
abdullah1854abdullah1854
1

xlsx

Generate Architectural Decision Records in structured Markdown format.

Community
Advanced
GeargrindadminGeargrindadmin

architecture

Analyze architectural trade-offs and document decisions with ADR templates.

Community
Intermediate