software-architect

Name: software-architect
Availability: InStock
Author: wonderslife

Design scalable architectures with documented trade-offs and ADRs.

13|3|Updated Apr 7, 2026

Search Tags:#design #architecture #scalability #adr #reliability #trade-offs

Ready to run

npx skills add https://github.com/wonderslife/pdd-skills-v3 --skill software-architect-wonderslife

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: software-architect
Source: https://github.com/wonderslife/pdd-skills-v3/tree/main/skills/expert/software-architect
Command: npx skills add https://github.com/wonderslife/pdd-skills-v3 --skill software-architect-wonderslife

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architects and engineering teams often struggle to consistently design scalable systems, evaluate trade-offs, and maintain architectural documentation across projects.

Core Features & Use Cases

High-level system design and pattern guidance for boundaries, interfaces, and data architecture decisions.
ADRs, decision frameworks, and collaboration workflows to document and align on architecture choices.
Reliability, scalability, security and evolution considerations for microservices, monoliths, and platform migrations.

Quick Start

Run the software-architect skill to outline a scalable system architecture for a new service.

Frequently Asked Questions about software-architect

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

FAQPage Schema

How do I design scalable system architectures and evaluate trade-offs consistently?▼

To design scalable architectures, you need a structured guide for high-level design, system boundaries, and data architecture. This approach evaluates trade-offs and maintains architectural documentation across projects for engineering teams.

What's the best way to document architectural decisions for microservices and platform migrations?▼

The best way to document architectural decisions is using ADRs and decision frameworks. These collaboration workflows align teams on architecture choices for microservices, monoliths, and platform migrations while ensuring reliability and security.

When do I need to define system boundaries and data architecture for a new service?▼

You need to define system boundaries and data architecture when outlining a scalable system for a new service. This high-level design process establishes interfaces, reliability planning, and scalability considerations before development begins.

Can I use this approach for both monolith and microservices reliability planning?▼

Yes, you can use this architecture design approach for both monolith and microservices reliability planning. It provides end-to-end guidance covering evolution considerations, security, and scalability across different architectural patterns and platform migrations.

How do I create an ADR to align engineering teams on architecture choices?▼

You create an ADR by applying decision frameworks and collaboration workflows that document architectural trade-offs. This structured approach ensures engineering teams align on architecture choices and design principles throughout the system evolution.

Why does system architecture design require documented trade-offs and design principles?▼

System architecture design requires documented trade-offs because evaluating scalability, reliability, and security constraints demands structured decision-making. Including design principles and ADRs ensures architectural choices remain transparent and maintainable across evolving platform migrations.