architect-design

Name: architect-design
Availability: InStock
Author: PhaniJ

Generate Google-style technical design documents for system architectures and integrations.

Updated Jun 29, 2026

Search Tags:#architecture #system design #engineering #design doc #well-architected #technical strategy

Ready to run

npx skills add https://github.com/phanijapps/engram --skill architect-design-phanijapps

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architect-design
Source: https://github.com/phanijapps/engram/tree/main/.agents/skills/architect-design
Command: npx skills add https://github.com/phanijapps/engram --skill architect-design-phanijapps

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill solves the problem of inconsistent, poorly reasoned, or advocacy-driven technical design by enforcing a rigorous, Google-style design doc process that prioritizes honest alternatives, risk mitigation, and well-architected construction.

Core Features & Use Cases

Structured Design Shaping: Guides the user through problem framing, constraint identification, and concept shaping before drafting.
Well-Architected Convergence: Automatically checks designs against cloud-agnostic pillars and workload-specific lenses (GenAI/Agentic, Serverless).
Use Case: Use this when you need to propose a new system architecture, weigh technical trade-offs for an integration, or document a complex NFR strategy for a tech-lead review.

Quick Start

Invoke the architect-design skill to begin drafting a design document for the new notification service architecture.

Frequently Asked Questions about architect-design

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

FAQPage Schema

How do I write a well-architected design doc for system architecture?▼

To write a well-architected design doc, frame the system architecture problem, identify constraints, and evaluate technical trade-offs honestly. This process enforces structured problem shaping and rigorous operational risk mitigation.

What is a Google-style technical design document?▼

A Google-style technical design document is a comprehensive system architecture proposal enforcing honest alternative evaluation, structured problem framing, and well-architected framework alignment for technical decision-making processes.

How do I evaluate technical trade-offs and risks for system design?▼

Evaluate technical trade-offs and risks for system design through rigorous trade-off analysis and operational risk assessment, ensuring honest alternative evaluation and well-architected convergence before finalizing the architecture.

Can I use this for serverless and GenAI workload architecture design?▼

Yes, the system design process automatically checks architectures against cloud-agnostic pillars and workload-specific lenses including GenAI/Agentic and Serverless frameworks to ensure well-architected convergence.

When do I need a formal design doc for technical strategy?▼

You need a formal design doc for technical strategy when proposing a new system architecture, weighing integration trade-offs, or documenting a complex non-functional requirement strategy for tech-lead review.

Best way to document complex system integrations and NFR strategies?▼

The best way to document complex system integrations and NFR strategies is using a Google-style design doc that enforces structured problem framing, honest alternative evaluation, and rigorous operational risk mitigation.