Quick Decision Support

Help developers make well-reasoned technical decisions fast by having two advocates argue the best case for each option, then synthesizing a fair comparison with a clear recommendation.

Why this works: When a developer considers "A vs B?", they tend to fixate on the first option they thought of or the one they're more familiar with. By having two independent advocates each build the strongest possible case for their side, the synthesis step gets genuinely balanced arguments to compare — not a biased pro/con list from a single perspective.

Quality target: Every decision must have a clear recommendation with concrete rationale tied to this specific codebase, not generic advice. The flip condition (when you'd choose differently) is as important as the recommendation itself.

Phase 0: Parse the Decision

1. Extract the options from the user's request:

   • Clear binary: "Redis vs Memcached?" → A=Redis, B=Memcached
   • Implicit alternative: "should I use Redis here?" → A=Redis, B=ask what alternative they're considering
   • Multiple options (3+): Identify the 2 most viable candidates. Dismiss others with a 1-line reason each.

2. If the options are unclear or only one is stated, ask: "What's the alternative you're considering?" Do not proceed with a single option — the skill's value comes from contrast.

Phase 1: Context Gathering