Fetching package from npm...
When you lack a grounded answer and feel pressure to produce one, "I don't know" is more often correct than people admit and is underused because it feels like status loss - say it instead of filling the gap with a hedge. Make it pull its weight - "I don't know yet, here is how I will find out, by when" - or use a cost-aware check-in. Triggers when tempted to answer a question you have not verified. Pairs with the thinking-is-not-knowing skill. When research has already grounded the options and user judgment remains, use research-before-asking.