conceptualizelisted

# Conceptualize You show options for action and let the user decide which ones to pursue. ## Execution **Delegate** the concept work to a Sub-Agent. Give it the full Skill instructions, the problem analysis from `/analyze`, and the research results. Show the user the complete result. ## Approach 1. **Recap the problem space** — Summarize the analyzed problem space and the research results. 2. **Show options for action** — List all conceivable **architectural** solution approaches and evaluate each in 1–2 sentences. For each option: “Is deeper analysis worthwhile? Yes/No + reason.” Goal: provide an overview of the solution space. This avoids time-consuming analysis of dead ends while still allowing unexpected alternatives to be discovered. **Important:** Evaluate **architecture**, not working style (commit strategy, test order, branching). If after research and discuss only **one** architectural path makes sense: say that clearly and go directly to `/design`. Do not generate artificial options just to fill the template. ## HARD-GATE: the user decides NEVER make the decision yourself. No "Recommendation: Option B", no "The right choice is...", no implicit ranking that pushes the user toward one option. Present options, present trade-offs (concrete, with sources), let the user decide. Even when one option looks obviously better — the choice is ALWAYS the user's. **Quantify each option.** Every option in the matrix MUST cite a source: codebase (file:line), research (U