alternative-solution-designer

Reframe complex problems into multiple low-friction alternative solution paths.

2|1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/AllanYiin/Amon --skill alternative-solution-designer-allanyiin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: alternative-solution-designer
Source: https://github.com/AllanYiin/Amon/tree/main/src/amon/resources/skills/alternative-solution-designer
Command: npx skills add https://github.com/AllanYiin/Amon --skill alternative-solution-designer-allanyiin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams reframing complex problems to uncover non-model alternatives and generate multiple viable paths that are practical and low-friction.

Core Features & Use Cases

  • Structure problem and challenge assumptions to decompose into components.
  • Generate at least 3 distinct solution types from different thinking styles (UI/UX, process, technical, or rule-based).
  • Provide a low-friction option suitable for quick piloting and decision making.
  • Include cross-domain analogies and explicit trade-offs to aid evaluation.

Quick Start

Explain the current problem scenario and output at least three alternative approaches with low-friction options.

Frequently Asked Questions about alternative-solution-designer

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

FAQPage Schema
How do I generate alternative solutions for a complex problem stuck on a single model-driven approach?

This approach identifies at least three distinct solution types from different thinking styles, such as UI/UX, process, technical, or rule-based. It also includes two cross-domain analogies and a clearly defined lowest-friction option for piloting.

How do I find a low-friction solution for quick piloting and decision making?

Find a low-friction solution for quick piloting by generating multiple viable paths and explicitly defining a lowest-friction option. This involves evaluating distinct solution types alongside cross-domain analogies to ensure practical, low-risk implementation.

Can I use cross-domain analogies to reframe rigid workflow processes?

This approach evaluates current approaches relying on a single model-driven solution or rigid process. It generates at least three distinct solution types and explicitly defines trade-offs to aid evaluation and decision making.

What is the best way to structure problem decomposition for decision-making?

By structuring problems this way, teams can uncover non-model alternatives and define a clearly lowest-friction option for piloting. This ensures generated paths are practical, diverse, and implementable across different thinking styles.

Does this alternative solution design approach work for technical and rule-based problem types?

The approach decomposes complex problems and challenges assumptions to produce multiple viable paths. It provides a low-friction option suitable for quick piloting across these different solution types.