wa:design-solution

Generate reviewed software architecture designs with cross-layer conflict resolution.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly produce a coherent software architecture design by orchestrating context gathering, specialist architecture work, cross-review conflict checks, and a finalized design document.

Core Features & Use Cases

  • Stage-based architecture planning: Loads project constants, research, and existing design artifacts, then delegates backend/frontend/UI design to specialist agents.
  • Cross-review for consistency: Runs backend-vs-frontend compatibility checks (data contracts, API alignment, performance concerns) and resolves conflicts with rationale.
  • Documentation + optional publishing: Writes a structured architecture document to docs/design and optionally publishes to Confluence when enabled.
  • Best fit use case: Planning a new feature or system (e.g., authentication, notification pipeline, or any non-trivial cross-cutting architecture change) where both backend and frontend decisions must match.

Quick Start

Run /design-solution with a feature or system description to generate a reviewed architecture document and supporting ADR candidates.

Frequently Asked Questions about wa:design-solution

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

FAQPage Schema
How do I generate a software architecture design document for a new feature?

To generate a software architecture design, run the skill with a feature description to orchestrate context gathering, specialist backend and frontend planning, and cross-review conflict checks. It produces a structured architecture document with consistent API contracts and component hierarchies.

How do you ensure API contract consistency between backend and frontend architecture plans?

API contract consistency is verified through cross-review conflict checks that analyze data contracts, API alignment, and performance concerns between backend and frontend plans. Conflicts are resolved with documented rationale before finalizing the architecture design.

Can I automatically publish architecture documentation to Confluence?

Yes, architecture documentation can be automatically published to Confluence when the publishing setting is enabled. The skill writes the structured architecture document to the design directory and conditionally pushes the content to Confluence.

What is the best way to plan a cross-cutting system architecture with UI/UX flows?

The best way to plan a cross-cutting system architecture is to use stage-based planning that delegates backend, frontend, and UI design to specialist agents. This ensures state, data-fetching patterns, and UI/UX flows remain consistent across all architectural layers.

When do I need a cross-review process for architecture design?

A cross-review process for architecture design is needed when planning non-trivial cross-cutting features where backend and frontend decisions must match. It validates data contracts and API alignment compatibility, resolving conflicts before documentation is finalized.