ultra-thinklisted

# ultra-think — Phase 3.6 Reasoning harness for complex decisions / diagnostics / architecture calls. Enforces Evidence-First labelling and adversarial stress-tests before issuing a recommendation with explicit confidence. ## Workflow ### Step 1 — Scope Check If the problem is ambiguous / underspecified, ask up to **3** clarifying questions through the current Host's native user-interaction surface. If the problem is simple, **skip the framework**, answer concisely, and mark downstream steps `completed` with note `"skipped: simple answer path"`. ### Step 2 — Evidence Gathering Every factual claim about tech/API/best-practices must be verified via: - Repo source (Read/Grep) - Official docs (Context7 MCP: `mcp__context7__query-docs`) - Community (Exa MCP: `mcp__exa__web_search_exa`) - Web search (fallback) Label each assertion: - **Fact** — verified, cite source (URL / file path) - **Inference** — deduced from facts (show the derivation chain) - **Speculation** — unverified; list verification steps the user can run **Iron law**: never trade accuracy for speed. Wrong-with-confidence > "I don't know + here's how to check". ### Step 3 — Multi-Perspective Analysis Generate **≥3 distinct approaches**. For each, apply whichever lenses are relevant: - **Technical** — feasibility, scalability, security, maintainability - **Business** — value, cost, time-to-market, competitive advantage - **User** — needs, experience, edge cases, accessibility - **System** — integration, depen