che-architect

Designs system architectures from business ideas through iterative five-step planning.

Updated May 12, 2026
One-click install
npx skills add https://github.com/laionazeredo/che-ai --skill che-architect-laionazeredo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: che-architect
Source: https://github.com/laionazeredo/che-ai/tree/main/skills/che-architect
Command: npx skills add https://github.com/laionazeredo/che-ai --skill che-architect-laionazeredo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a high-level business idea into a concrete technical blueprint is hard: teams often jump into code without defining intent, roadmap, module boundaries, or infrastructure, leading to rework and over-engineering. This Skill guides an iterative architecture process that produces durable, navigable design documents. ## Core Features & Use Cases - Five-Step Iterative Design: Discovery and intent capture, roadmap planning, architecture and module design, infrastructure and resource estimation, then final blueprint artifacts. - Structured Architecture Documents: Generates intent.md, roadmap.md, and architecture.md with mandatory sections including C4 diagrams, ERDs, security and compliance analysis, and an ADR index. - Quality Gates: Enforces KISS/YAGNI checks, portability checks, and module cohesion checks to prevent over-engineering. - Use Case: A founder describes a SaaS booking platform idea; the Skill walks through personas, a Mermaid user journey map, a buy-vs-build matrix, C4 context and container diagrams, a macro ERD, and a cost-estimated roadmap saved to the project workspace. ## Quick Start Ask the assistant to help architect a complete system from your business idea, starting with an intent document and proceeding step by step through roadmap, architecture, and infrastructure planning.

Frequently Asked Questions about che-architect

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

FAQPage Schema
How do I turn a business idea into a system architecture?▼

Follow the five-step iterative workflow: capture intent and personas, plan a phased roadmap, design modules with C4 diagrams and an ERD, estimate infrastructure and resources, then save the final blueprint artifacts. Each step asks for feedback before proceeding.

What diagrams should a software architecture document include?▼

A complete architecture document should include a user journey map, feature map, C4 context, container, and component diagrams, plus an entity relationship diagram. This Skill generates all of them as Mermaid code blocks within architecture.md.

Does this Skill decide between monolith and microservices?▼

Yes, pattern selection between monolith, microservices, and serverless is part of Step 3, along with bounded context module mapping. The KISS/YAGNI quality gate prevents recommending distributed systems for simple applications.

Can it estimate cloud costs and engineering effort?▼

Yes, Step 4 produces resource estimation including monthly cost ranges and effort in man-months or sprints. It also covers cloud provider selection, CI/CD strategy, and observability planning.

When should I not use a full architecture planning workflow?▼

Skip the full workflow for small scripts, prototypes, or single-feature changes where a five-step design process adds overhead. The Skill itself enforces YAGNI and warns against over-engineering simple requests.