architect

Plan and document software architecture decisions with a structured decision framework.

Updated Jan 26, 2026
One-click install
npx skills add https://github.com/Barryrn/saas-setup --skill architect-barryrn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/Barryrn/saas-setup/tree/main/.claude/skills/architect
Command: npx skills add https://github.com/Barryrn/saas-setup --skill architect-barryrn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of planning and documenting software architecture decisions.

Core Features & Use Cases

  • Define module boundaries and select architectural patterns (layered, modular, event-driven) for a system.
  • Evaluate build vs buy decisions and monolith vs distributed designs to guide roadmap and risk.
  • Create a decision log that records tradeoffs, assumptions, and constraints to inform future work.

Quick Start

Use the architect skill to structure a system design discussion and capture decisions using a standard architecture template.

Frequently Asked Questions about architect

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

FAQPage Schema
How do I document software architecture decisions and tradeoffs?

Document software architecture decisions by recording tradeoffs, assumptions, and constraints in a decision log. This enforces a decision framework based on principles like separation of concerns to inform future work.

What is the best way to choose between a monolith and distributed system design?

Evaluating monolith versus distributed system design involves analyzing tradeoffs, risks, and roadmap impact. A decision framework guides this comparison to ensure the selected architecture aligns with project constraints.

How do I define module boundaries using architectural patterns?

Define module boundaries by selecting architectural patterns such as layered, modular, or event-driven designs. Applying single responsibility and separation of concerns principles ensures clear boundaries and robust system structure.

Can I use this to evaluate build versus buy decisions for system architecture?

Yes, you can evaluate build versus buy decisions for system architecture. The decision framework provides guidance for analyzing constraints and tradeoffs to determine whether to build internally or purchase externally.

When do I need a formal decision log for system design?

You need a decision log for system design when capturing tradeoffs and outcomes is necessary to inform future work. It records assumptions and constraints to maintain clarity across evolving architecture decisions.