architect

Name: architect
Availability: InStock
Author: denissvgn

Automates architecture decision records and system design documentation for complex software projects.

Updated Jan 14, 2026

Search Tags:#architecture #system design #API design #governance #ADR #design documents #architect

Ready to run

npx skills add https://github.com/Denissvgn/project-team-ag --skill architect-denissvgn

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/Denissvgn/project-team-ag/tree/main/.agent/skills/architect
Command: npx skills add https://github.com/Denissvgn/project-team-ag --skill architect-denissvgn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Architect skill helps teams define and communicate robust system architecture, decide on architectural directions, and document decisions as Architecture Decision Records (ADRs). It reduces ambiguity in design and accelerates handoffs by producing clear architectural artifacts.

Core Features & Use Cases

ADR Creation: Document architectural decisions with clear context, options, and tradeoffs.
System Design: Outline high-level components, relationships, and data flows.
API Contracts: Define endpoints, data models, and interface boundaries for teams.

Quick Start

Initiate a design session with requirements describing the target system's scale and constraints, then generate ADRs and a system design outline.

Frequently Asked Questions about architect

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

FAQPage Schema

How do I create Architecture Decision Records for a multi-team software project?▼

Architecture Decision Records are generated by automating architectural decision making and documentation. The process captures context, options, and tradeoffs to produce clear artifacts that reduce ambiguity and accelerate handoffs across frontend, backend, and security teams.

What is the best way to outline system design and API contracts during the planning phase?▼

System design and API contracts are outlined by defining high-level components, relationships, data flows, endpoints, data models, and interface boundaries. This establishes consistent governance and clear architectural artifacts during the planning, design, and hand-off phases.

Do I need to provide specific requirements to start an architecture design session?▼

You need to initiate a design session with requirements describing the target system's scale and constraints. Providing these inputs allows the system to generate accurate ADRs and a comprehensive system design outline tailored to your project.

Can I use this approach to define interface boundaries for frontend, backend, and security teams?▼

Interface boundaries for frontend, backend, and security teams are defined by generating API contracts and data models. This enables consistent governance across multiple teams by satisfying requirements for clear API specifications and architectural artifacts.

What limitations exist when automating system design diagrams and data models?▼

Automating system design diagrams and data models applies specifically to multi-team software projects requiring ADRs and API contracts. The process focuses on planning, design, and hand-off phases, meaning it produces architectural artifacts rather than implementation code.

Why does the Architect skill focus on ADRs instead of generating code?▼

The Architect skill focuses on ADRs and system design because it solves the problem of defining and communicating robust system architecture. It reduces ambiguity in design and accelerates handoffs by producing clear architectural artifacts rather than executable code.