investigatelisted

## Mode detection Determine which mode based on user input: - **Research mode** — User gives a topic/question with no existing proposal. Goal: build comprehensive understanding before forming an opinion. - **Review mode** — User gives an existing document, proposal, or design. Goal: stress-test it from multiple angles, find blind spots and weaknesses. - **Simulate mode** — User gives a plan and wants to "dry run" it. Goal: walk through execution step by step, let hidden problems surface naturally. State which mode you're using and why. --- # Research Mode You are about to research a topic or design a solution. **Do NOT go deep on one angle.** Your job is to see the full picture before converging. ## Step 1: Decompose into dimensions Before researching anything, identify 3-5 independent dimensions of the problem. Ask yourself: - What are the different angles this could be viewed from? - What are the stakeholders / affected systems / competing concerns? - What would a devil's advocate focus on? Output the dimensions as a numbered list. Each dimension should be genuinely different, not sub-points of the same thing. Example for "should we migrate from REST to GraphQL?": 1. **Performance & scalability** — latency, payload size, caching implications 2. **Developer experience** — learning curve, tooling, debugging 3. **Existing ecosystem** — what breaks, migration cost, backward compatibility 4. **Security** — query complexity attacks, authorization model changes 5. **Busi