architecture

Document architecture decisions using ADR templates and trade-off analysis.

1|1|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/DriveConnect-alpha/DriveConnect --skill architecture-driveconnect-alpha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/DriveConnect-alpha/DriveConnect/tree/main/.agent/skills/architecture
Command: npx skills add https://github.com/DriveConnect-alpha/DriveConnect --skill architecture-driveconnect-alpha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture decisions can become opaque and hard to trace, leading to misaligned outcomes and rework. This skill provides a structured framework (ADR, context discovery, and pattern references) to capture rationale and keep design decisions aligned with constraints.

Core Features & Use Cases

  • ADR templates and decision records to document rationale and trade-offs.
  • Context discovery prompts to gather project information before designing.
  • Pattern and reference references to guide pattern selection and best practices.

Quick Start

Open this skill and start by drafting an ADR for your current architecture decision.

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 to reduce ambiguity?

Apply ADR workflows to document architecture decisions, capturing rationale and trade-offs to reduce ambiguity. This structured approach improves traceability and keeps design choices aligned with project constraints through linked references and templates.

What is an ADR and when do I need to write one?

An ADR is an architecture decision record that documents rationale and trade-offs for a design choice. You need to write one when making significant architecture decisions to ensure context and constraints remain traceable for future reference.

How do I capture project context before selecting architecture patterns?

Capture project context using context discovery prompts before designing. This gathers essential project information, enabling accurate pattern selection and trade-off analysis that aligns your architecture decisions with actual system constraints.

What's the best way to track architecture trade-offs across systems?

Track architecture trade-offs across systems using decision records and linked references. This provides a structured framework to document rationale, maintain alignment with constraints, and ensure design decisions remain transparent and traceable.

Can I use this skill for pattern selection and best practices guidance?

Yes, you can use this skill for pattern selection. It includes pattern and reference guides to help you select best practices, applying trade-off analysis and context discovery to ensure the chosen patterns fit your system constraints.