034-architecture-design-exploration

Compare feasible architecture approaches and recommend a direction with user approval.

423|90|Updated Feb 8, 2025
One-click install
npx skills add https://github.com/jabrena/plinth --skill 034-architecture-design-exploration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 034-architecture-design-exploration
Source: https://github.com/jabrena/plinth/tree/main/skills/034-architecture-design-exploration
Command: npx skills add https://github.com/jabrena/plinth --skill 034-architecture-design-exploration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps to explore and clarify technical architecture design options before proceeding with ADRs, specifications, or implementation plans.

Core Features & Use Cases

  • Technical Design Exploration: Inspects repository context and clarifies technical ambiguities.
  • Approach Comparison: Compares two or three feasible approaches with trade-off analysis.
  • Direction Recommendation: Recommends a direction with explicit rationale and user approval.
  • ADR Identification: Identifies ADR candidates and unresolved questions.
  • Use Case: Utilize this skill when facing a complex design challenge and need to explore various options before making a decision.

Quick Start

Start a design exploration for a new feature by running:

/start-design-exploration -feature "new_feature"

Frequently Asked Questions about 034-architecture-design-exploration

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

FAQPage Schema
How do I explore architecture design options before writing an ADR?

To explore architecture design options before writing an ADR, inspect the repository context, compare two or three feasible approaches with trade-off analysis, and recommend a direction with explicit rationale. This process identifies ADR candidates and unresolved questions.

What is the best way to compare technical approaches for a new feature?

The best way to compare technical approaches for a new feature is to evaluate two or three feasible solutions with explicit trade-off analysis. This clarifies technical ambiguities and recommends a specific direction with rationale before proceeding to specifications.

How do I clarify technical ambiguities in my repository before implementation?

To clarify technical ambiguities in your repository before implementation, inspect the repository context to evaluate various solutions. This approach compares feasible approaches with trade-offs and obtains user approval before proceeding with implementation plans.

Can I use design exploration to identify ADR candidates and unresolved questions?

Yes, you can use design exploration to identify ADR candidates and unresolved questions. It compares feasible approaches with trade-off analysis and recommends a direction with explicit rationale for user approval before proceeding with specifications.

When do I need to start a design exploration for architecture decisions?

You need to start a design exploration for architecture decisions when facing a complex design challenge and needing to explore various options before making a decision. It utilizes trade-off analysis and direction recommendations with explicit rationale to obtain user approval.