kwp-engineering-architecture

Create and evaluate Architecture Decision Records documenting technical trade-offs.

7|5|Updated May 7, 2026
One-click install
npx skills add https://github.com/14790897/MiQi --skill kwp-engineering-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kwp-engineering-architecture
Source: https://github.com/14790897/MiQi/tree/main/miqi/skills/kwp/engineering/architecture
Command: npx skills add https://github.com/14790897/MiQi --skill kwp-engineering-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the ambiguity and lack of documentation in technical decision-making by providing a structured framework for creating and evaluating Architecture Decision Records (ADRs).

Core Features & Use Cases

  • ADR Creation: Generate standardized documentation for technical choices, including trade-offs and consequences.
  • Design Evaluation: Analyze microservices proposals, system designs, or technology migrations (e.g., Kafka vs SQS).
  • Use Case: When your team is debating a new database schema or infrastructure change, use this skill to objectively compare options and document the final decision for future reference.

Quick Start

Use the architecture skill to create an ADR comparing the trade-offs between using PostgreSQL and MongoDB for our new user service.

Frequently Asked Questions about kwp-engineering-architecture

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

FAQPage Schema
How do I document architecture decisions for a new system design?

You create Architecture Decision Records to objectively document technical trade-offs, evaluate technology options, and record final system design choices for consistent project history.

What is the best way to compare technology choices like Kafka vs SQS for infrastructure?

You evaluate technology migrations by analyzing trade-offs between options like Kafka and SQS, then documenting the objective comparison and final selection in an Architecture Decision Record.

Can I use this skill to evaluate a microservices proposal?

Yes, you can analyze microservices proposals and system designs by evaluating trade-offs and documenting the architectural choices using Architecture Decision Records.

Do I need project documentation and file system tools to maintain design history?

Yes, maintaining a consistent design history requires access to existing project documentation and file system tools to store and manage the generated Architecture Decision Records.

How do I create an ADR for a database schema debate?

You create an ADR for a database schema debate by objectively comparing proposed options, analyzing technical trade-offs, and documenting the final decision for future reference.

When should I use Architecture Decision Records in the software engineering lifecycle?

Use Architecture Decision Records during architectural planning, technology selection, and design reviews to resolve ambiguity and provide a structured framework for technical decision-making.