wa:design-arch

Generate system architecture plans with service decomposition and data flow diagrams.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-design-arch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wa:design-arch
Source: https://github.com/jeremy-newhouse/eck-e2e-weather-app/tree/main/.claude/skills/design-arch
Command: npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-design-arch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Design Architecture skill turns a feature or system description into a structured, end-to-end architecture plan, including service decomposition, data flow, security architecture, and concrete documentation artifacts.

Core Features & Use Cases

  • Service decomposition & data flow: Produces a clear split of responsibilities across services plus how data moves between them.
  • Security architecture: Defines authentication/authorization and data protection boundaries aligned to the project context.
  • Architecture documentation output: Writes a ready-to-review artifact at docs/{feature}/ARCHITECTURE.md and optionally attempts Confluence publishing.

Quick Start

Run /design-arch and pass your feature or system description to generate docs/{feature}/ARCHITECTURE.md.

Frequently Asked Questions about wa:design-arch

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

FAQPage Schema
How do I generate system architecture documentation from a feature description?

System architecture documentation is generated by processing a feature description into service decomposition, data flow diagrams, infrastructure decisions, and security architecture. The resulting plan is written directly to an ARCHITECTURE.md file for review.

What is the best way to design service decomposition and data flow for a new system?

Service decomposition and data flow design splits responsibilities across services and maps data movement between them. This approach aligns with project tech stack variables and outputs concrete architecture documentation artifacts for review.

Can I define security architecture and data protection boundaries based on my project context?

Security architecture and data protection boundaries are defined based on your project context. The process generates authentication, authorization, and data protection guidance aligned with the specific tech stack and infrastructure decisions.

Does the architecture design workflow require prior artifacts or functional requirements?

Architecture design workflows read project constants and available prior artifacts to ensure alignment. They optionally accept FRD acceptance criteria to coordinate specialist agent dispatch and enforce plan-mode requirements during generation.

How do I structure infrastructure decisions and architecture documentation for a tech stack?

Infrastructure decisions and architecture documentation are structured by enforcing consistent documentation standards. The process aligns decisions with project tech stack variables and writes the resulting architecture plan to the correct docs feature path.