wa:design-discovery

Validate architecture and design decisions through collaborative technical discovery.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams avoid building the wrong architecture by collaboratively discovering requirements, constraints, and tradeoffs before implementation.

Core Features & Use Cases

  • Guided multi-stage discovery workflow: prepares context, explores gated technical domains, synthesizes decisions, and documents outcomes.
  • Domain gating by project readiness and mode: selects the right breadth of discovery (required, light-pass, conditional, strict) based on the project type and rigor level.
  • Traceable design outputs: produces a documented artifact at docs/{feature}/DESIGN-DISCOVERY.md including architecture decisions, constraints, integration requirements, and open technical questions.
  • Use case: When adding a feature like OAuth2 login/session management, run discovery to confirm domain decisions (architecture, data model, security, operations, and risks) and capture AC-ID implications before design/engineering begins.

Quick Start

Use /design-discovery with a clear feature description to generate docs/{feature}/DESIGN-DISCOVERY.md with confirmed architecture decisions and open technical questions.

Frequently Asked Questions about wa:design-discovery

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

FAQPage Schema
What is architecture validation in technical design discovery?

Design discovery generates a documented DESIGN-DISCOVERY artifact that captures confirmed architecture decisions, integration requirements, constraints, and open technical questions for cross-referencing implementation criteria.

How do I validate architecture decisions before starting feature implementation?

Run a guided multi-stage discovery workflow with a clear feature description to explore gated technical domains, synthesize decisions, and document outcomes. This produces a traceable design artifact confirming your architecture before engineering begins.

Can I adjust the rigor of technical tradeoff analysis for different project types?

Yes, domain gating selects the breadth of discovery—required, light-pass, conditional, or strict—based on your project type and rigor mode. This ensures the architecture validation process matches your specific project readiness level.

Does architecture validation work for complex API integration and security design features?

Yes, guided discovery validates domain decisions across architecture, data model, API integration, security design, operations, and risk domains. It is applicable for any feature description requiring comprehensive technical tradeoff analysis.

What is the best way to document technical tradeoffs and open questions during design?

Use guided discovery to output a documented artifact at docs/{feature}/DESIGN-DISCOVERY.md. This file captures architecture decisions, constraints, integration requirements, and open technical questions for AC-ID cross-referencing.

When should I avoid running a full technical discovery workflow?

You should skip strict full discovery for low-readiness projects where a light-pass or conditional gating mode is more appropriate. The workflow requires an Opening Move with a context briefing and discovery agenda to properly execute.