engineering-architecture

Create architecture decision records and evaluate system design proposals with trade-off analysis.

Updated May 26, 2026
One-click install
npx skills add https://github.com/avel123111/triplanio --skill engineering-architecture-avel123111
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: engineering-architecture
Source: https://github.com/avel123111/triplanio/tree/main/.claude/skills/engineering-architecture
Command: npx skills add https://github.com/avel123111/triplanio --skill engineering-architecture-avel123111

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering teams often make technology choices informally, losing the reasoning behind decisions and making future reviews difficult. This Skill structures architecture decisions into a consistent ADR format with documented options, trade-offs, and consequences. ## Core Features & Use Cases - ADR Creation: Generate a complete Architecture Decision Record with status, context, decision, options comparison, trade-off analysis, and action items. - Design Evaluation: Review an existing system design proposal or microservices plan against stated constraints. - System Design from Requirements: Design a new component, such as a notification system, starting from requirements and non-functional constraints like latency, cost, and scale. - Use Case: When debating Kafka versus SQS for an event bus, invoke the Skill to produce a side-by-side options table with pros, cons, and a documented decision your team can reference later. ## Quick Start Ask the assistant to create an ADR comparing Kafka and SQS for your event bus, including your scale and timeline constraints.

Frequently Asked Questions about engineering-architecture

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

FAQPage Schema
How do I write an architecture decision record?

Provide the decision or system to design, and the Skill generates an ADR with status, date, deciders, context, decision, options considered, trade-off analysis, consequences, and action items. Stating constraints upfront improves the output.

How do I compare two technologies like Kafka vs SQS?

Name both options explicitly and include constraints such as throughput targets or deadlines. The Skill produces a per-option assessment table covering complexity, cost, scalability, and team familiarity, plus pros, cons, and a trade-off analysis.

Can this Skill review an existing system design proposal?

Yes, it supports an evaluation mode where you paste a design proposal, such as a microservices plan, and it reviews the design against your stated requirements and constraints rather than creating a new ADR.

What information should I include for better architecture analysis?

Include constraints like shipping deadlines and scale targets, name the candidate options even if you lean toward one, and list non-functional requirements such as latency, cost, team expertise, and maintenance burden.

When should I use the system-design skill instead of an ADR?

The ADR format fits documenting a specific decision with options and consequences. For deeper frameworks on requirements gathering, scalability analysis, and trade-off evaluation, the Skill itself points to the companion system-design skill.