What problem does it solve? New or ambiguous terms often collapse distinct concepts—such as a threshold value, a condition, and an event—into one fluent label, silently distorting later design, investigation, or code. This Skill performs a semantic preflight that grounds each material term in a concrete referent before any naming happens. ## Core Features & Use Cases - Grounding-then-Naming workflow: Builds a label-free Grounding table (referent, semantic role, relationships, uncertainty) first, then a Naming table with established terms, proposals, or concrete wording. - Explicit state contract: Reports Ready, Decision required, or Blocked so unresolved public-contract meanings are escalated while low-impact local naming completes without unnecessary confirmation. - Handoff boundary: Returns a referent-and-naming contract to the originating workflow without drafting the downstream document, design, or code, and without creating unauthorized sidecar files. - Use Case: Before naming a public SDK boolean streaming, use this Skill to separate whether it means the caller requested streaming, the server accepted it, bytes are flowing, or streaming completed—then present the decision-relevant question instead of silently choosing. ## Quick Start Before designing this feature, perform a semantic preflight for the term compression point and separate the numeric limit, the reached-limit condition, and the summarization event into a referent table with naming constraints.
