What problem does it solve? Teams often jump straight to solutions without understanding the real problem, treating symptoms instead of root causes. This Skill enforces a structured diagnosis phase that distinguishes hypotheses from facts, surfaces hidden risks, and identifies what must be validated before any action plan is made. ## Core Features & Use Cases - Structured Diagnosis: Produces a fixed analysis format covering executive summary, core problem, symptoms, probable root causes, impacts, risks, fragile premises, and required validations. - Critical Reasoning: Challenges assumptions, compares alternatives, exposes trade-offs, and evaluates scalability, governance, adoption, and operational cost. - Explicit Hypotheses: Works with incomplete context by stating assumptions clearly and flagging what needs confirmation. - Use Case: A manager says "we have too much rework between departments." The Skill structures the situation, separates observable symptoms from probable causes, lists operational and governance impacts, and asks whether to advance to the gtsi-plan skill for an action plan. ## Quick Start Ask the assistant to analyze an operational problem, for example: "Analyze why our ticket queue keeps growing and identify the root causes before we plan anything."
