What is an ADR and why does this skill use them?

An Architecture Decision Record (ADR) is a document that captures an important architectural decision made along with its context and consequences. This skill uses them to ensure technical choices are documented, transparent, and easy for teams to follow.

How does the technology evaluation framework work?

It uses a weighted scoring system (Fit, Maturity, Team Skills, Cost, etc.) to help you objectively decide between different tools or platforms based on your specific project needs.

Can this skill help with microservices architecture?

Yes, it provides guidance on common microservice patterns such as gRPC for communication, the Saga pattern for distributed transactions, and CQRS for data optimization.

What architecture principles does this skill follow?

It prioritizes Separation of Concerns, Defense in Depth, Design for Change (loose coupling), and Observability First (logging, metrics, and tracing).

Software Architecture & System Design

Name: Software Architecture & System Design
Author: jpoley

byjpoley

•

学習とドキュメンテーション

Guides system design and architectural decision-making using standardized ADR formats and Spec-Driven Development principles.

This skill empowers Claude to act as a senior software architect, facilitating complex system design, technology evaluation, and formal documentation. It implements a structured Architecture Decision Record (ADR) framework to capture technical rationale, ensures adherence to core principles like separation of concerns and observability, and provides comprehensive checklists for scalability and non-functional requirements. Ideal for teams practicing Spec-Driven Development, it helps bridge the gap between high-level requirements and robust technical implementation.

主な機能

01Standardized ADR (Architecture Decision Record) generation and management

02Weighted technology evaluation framework for objective tool selection

03Scalability and resilience pattern checklists including Circuit Breakers and CQRS

045 GitHub stars

05Non-functional requirement (NFR) documentation for performance and security

06Integration with Spec-Driven Development and backlog management workflows

ユースケース

01Designing high-level system architectures with a focus on scalability, observability, and maintainability

02Documenting critical technical decisions to maintain a historical record of architectural rationale

03Evaluating and comparing multiple technologies or frameworks for a new project or migration

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add jpoley/flowspec architect

For use in Claude.ai and ChatGPT

Download Skill