skills.rest
eugenelim
eugenelimCOMMUNITY
Explore all skills by this author →
GitHub

architect-design

Generate Google-style architecture design documents for system and integration decisions.

15|5|Updated May 4, 2026
Search Tags:#architecture#system design#cloud#review#agentic#design-doc#tradeoffs
One-click install
npx skills add https://github.com/eugenelim/agent-ready-repo --skill architect-design-eugenelim
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architect-design
Source: https://github.com/eugenelim/agent-ready-repo/tree/main/packs/architect/.apm/skills/architect-design
Command: npx skills add https://github.com/eugenelim/agent-ready-repo --skill architect-design-eugenelim

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps you turn an open-ended architecture or integration question into a disciplined, reviewable design document instead of a vague proposal or a half-finished plan.

Core Features & Use Cases

  • Shape the problem first: Clarifies goals, constraints, tradeoffs, and open questions before drafting the full solution.
  • Produce a structured design doc: Generates a Google-style document with context, goals, non-goals, proposal, alternatives, risks, rollout, and open questions.
  • Strengthen the decision quality: Surfaces realistic alternatives, operational risks, and cross-cutting concerns so the design can survive review.
  • Use case: Ideal for system architecture decisions, technology selection, platform integration choices, and agentic or cloud design discussions.

Quick Start

Ask the skill to help you frame and write a design document for your architecture decision, including the constraints, tradeoffs, and rollout plan.

Frequently Asked Questions about architect-design

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

FAQPage Schema
How do I structure an architecture design doc for system and integration decisions?▼

An architecture design doc requires clear goals, constraints, alternatives, risks, rollout planning, and open questions. A Google-style format structures context, non-goals, proposals, and cross-cutting concerns to ensure the system design survives technical review.

What should I include in a cloud workload design proposal before review?▼

A cloud workload design proposal must include problem framing, realistic alternatives, operational risks, and rollout planning. Clarifying tradeoffs and cross-cutting concerns before drafting the solution ensures the architecture decision is disciplined and review-ready.

How do I frame tradeoffs and alternatives for a technology selection design document?▼

Framing tradeoffs for a technology selection design document involves clarifying goals and constraints first, then surfacing realistic alternatives and operational risks. This disciplined approach turns open-ended integration questions into structured, reviewable proposals.

Can I use a structured design doc format for agentic workload architecture decisions?▼

Yes, a structured design doc format applies directly to agentic workload architecture decisions. It captures problem framing, technology selection, and rollout planning, ensuring that agentic design discussions produce a review-ready proposal with open questions.

When do I need a formal architecture design document instead of a proposal?▼

You need a formal architecture design document when an open-ended integration or system architecture question requires disciplined review. It replaces vague proposals by enforcing clear goals, non-goals, alternatives, and risk assessments before implementation begins.

Related Skills

Explore More Software Engineering Skills→
proyecto26proyecto26
42

requirements-scoping

Structure ambiguous system design prompts into functional requirements, non-functional constraints, and out-of-scope boundaries.

Official
Intermediate
OmexITOmexIT
13

ticket-breakdown

Convert PRD or design docs into epics, tickets, and acceptance criteria.

Community
Intermediate
Pixel-Process-UGPixel-Process-UG
1

senior-architect

Guide system design, ADR creation, and scalability planning.

Official
Advanced
product-on-purposeproduct-on-purpose
527

develop-adr

Generate Architecture Decision Records using the Nygard-style ADR template.

Official
Basic