architect

Design system architecture blueprints for subsystems and APIs.

Updated Mar 26, 2026

Search Tags:#design #interfaces #trade-offs #system-architecture #data-models #apis #team-alignment

Ready to run

npx skills add https://github.com/benediktms/overmind --skill architect-benediktms

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/benediktms/overmind/tree/main/cli/claudecode-plugin/skills/architect
Command: npx skills add https://github.com/benediktms/overmind --skill architect-benediktms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designs system architecture decisions to define components, APIs, and data models before implementation, reducing ambiguity and rework across teams.

Core Features & Use Cases

Architecture decision documentation: outline components, interfaces, data models, and API contracts.
Trade-off analysis: compare options, evaluate risks, and document rationale.
Team alignment: ensure clear ownership and responsibility boundaries for subsystems.

Quick Start

Provide a high-level system boundary with key APIs and data models, including interfaces, contracts, and non-functional requirements.

Frequently Asked Questions about architect

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

FAQPage Schema

How do I define scalable system architecture and API contracts for a new subsystem?▼

System architecture blueprints outline components, interfaces, and data models for new subsystems. They are needed during early-stage design to define API contracts and reduce implementation ambiguity across teams.

How do I document architecture trade-offs when evaluating multiple design options?▼

Document architecture trade-offs by comparing options, evaluating risks, and recording the rationale. This ensures maintainability constraints are met and provides clear ownership boundaries for team alignment.

What is the best way to align teams on system boundaries and API contracts?▼

The best way to align teams is defining comprehensive system architecture blueprints with explicit boundaries and well-defined interfaces. This establishes clear ownership and responsibility for each subsystem.

What do I need to provide to start designing system architecture and data models?▼

To start designing system architecture, you provide a high-level system boundary with key APIs and data models. Including interfaces, contracts, and non-functional requirements ensures comprehensive trade-off analysis.

When should I not use early-stage system architecture design?▼

Early-stage system architecture design should be avoided when implementation is already underway without ambiguity. It targets pre-implementation phases to define components, evaluate trade-offs, and establish boundaries before coding begins.