Solution Design — Orchestrator

Strategy — Step 2 of 4. Brainstorms targeted solutions and ranks them with evidence-backed scoring.

Core Question: "What's the highest-impact thing we can do about this?"

Critical Gates — Read First

1. Every initiative hypothesis MUST name the root cause. Generic growth ideas produce low-impact, unfocused initiatives. If the hypothesis "because" clause doesn't reference the confirmed root cause, the initiative is untethered.
2. Force-rank BEFORE scoring — ranking prevents "everything is a 6." The forced ranking sets the ceiling for ICE scores. If you ranked it #1, its ICE should be highest.
3. Anti-generic test is mandatory — "would this help ANY company?" Delete the root cause reference from an initiative. If it still makes sense for any company, it's generic. Rewrite.
4. ≤3 initiatives above cut line — force the constraint. More than 3 active initiatives means none get full attention. Parked initiatives have their turn after the current batch ships.

Inputs Required

• Root cause from .agents/problem-analysis.md