architect

Design software architectures with clear boundaries, data ownership, and failure handling.

2|Updated Mar 16, 2026

Search Tags:#architecture #deployment #microservices #observability #boundaries #system-design #failure-management

Ready to run

npx skills add https://github.com/chicongst/agent-skills-installer --skill architect-chicongst

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/chicongst/agent-skills-installer/tree/main/skills/architect
Command: npx skills add https://github.com/chicongst/agent-skills-installer --skill architect-chicongst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designs robust software architectures by emphasizing clear boundaries, defined data ownership, and failure-aware operability.

Core Features & Use Cases

Define service boundaries and data ownership to prevent data silos and unclear ownership.
Plan for failure with retries, circuit breakers, and sagas to maintain availability under partial failures.
Design for operability with observability, reversible deployments, and horizontal scaling to support real-world ops.
Produce architecture decisions and outputs using a consistent template and clear evaluation criteria.

Quick Start

Describe an architecture design for the requested system using the Architecture Template.

Frequently Asked Questions about architect

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

FAQPage Schema

How do I design microservices with clear boundaries and data ownership?▼

Define microservices boundaries by establishing strict data ownership to prevent silos, using an architecture template that enforces clear service separation and data governance for robust system design.

What is the best way to handle failure management in event-driven architectures?▼

Failure management in event-driven architectures requires planning for partial failures using retries, circuit breakers, and sagas to maintain availability and ensure robust operability under real-world conditions.

How do I plan for operability and observability when refactoring a monolith?▼

Plan monolith refactoring for operability by prioritizing observability, reversible deployments, and horizontal scaling to support real-world operations during the transition to distributed systems.

Can I use this architecture design guidance for both new deployments and system refactors?▼

Yes, architecture design guidance applies to both new deployments and refactors, constraining outputs to follow a consistent template that emphasizes clear boundaries, data ownership, and safe rollouts.

What are the limitations of designing system architecture without a consistent template?▼

Designing system architecture without a consistent template risks unclear ownership, data silos, and poor failure handling, lacking the structured evaluation criteria needed for safe rollouts and observability.