architecture-design-contest

Compare architecture options and recommend a final design direction.

Updated Mar 19, 2026

Search Tags:#architecture #trade-offs #decision-making #design-review #code-exploration #design-contest

Ready to run

npx skills add https://github.com/japurcell/skills --skill architecture-design-contest

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-design-contest
Source: https://github.com/japurcell/skills/tree/main/skills/architecture-design-contest
Command: npx skills add https://github.com/japurcell/skills --skill architecture-design-contest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture design contest helps teams generate multiple competing designs for a feature, compare trade-offs, and clearly recommend the best direction before implementation.

Core Features & Use Cases

Frame the design problem succinctly with goals, constraints, unknowns, and decision criteria.
Run 2+ parallel architecture explorations against the current codebase and documentation, then synthesize diverse designs and a final recommendation.
Provide an explicit comparison highlighting trade-offs, risks, and the recommended path, including a migration plan if needed.

Quick Start

Frame the problem, initiate parallel architecture explorations across the codebase, and deliver a clear, justified recommendation.

Frequently Asked Questions about architecture-design-contest

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

FAQPage Schema

What is architecture design-space exploration and when do I need it?▼

Architecture design-space exploration identifies multiple competing designs for a feature and compares their trade-offs to guide final selection. It is needed when you want alternatives before coding or require an RFC-level review to inform architectural direction.

How do I compare architecture trade-offs before starting implementation?▼

To compare architecture trade-offs, frame the design problem with goals and constraints, then run parallel explorations against your codebase. This synthesizes diverse designs into an explicit comparison highlighting risks, trade-offs, and a final recommended path.

Can I use this approach to review an existing codebase before deciding on a new feature?▼

Yes, design-space exploration requires grounding in the current codebase and documentation. Multiple subagents explore the existing code in parallel to ensure the generated architecture options are viable within your specific technical environment.

What's the best way to evaluate competing software architecture options?▼

The best way to evaluate competing architecture options is to run 2 or more parallel architecture explorations and synthesize the results. This delivers an explicit, opinionated recommendation that highlights trade-offs, risks, and a migration plan if needed.

Does this method provide a clear recommendation or just a list of design alternatives?▼

This method provides a clear, opinionated recommendation, not just a list of alternatives. It frames the design problem with decision criteria, compares trade-offs across parallel explorations, and synthesizes a final recommended direction to guide implementation.

When should I not use parallel architecture exploration for design reviews?▼

You should avoid parallel architecture exploration when your design problem lacks clear goals, constraints, or decision criteria, as the synthesis relies on framing the problem succinctly to generate viable competing designs and a justified recommendation.