Fetching package from npm...
Research and carry decisions before asking the user. Use for ambiguous requirements, missing specifications, ‘which approach’ or ‘should I use X or Y’ choices, or taste, priority, private facts, credentials, or authorization that remain after proportionate research. Present viable options, tradeoffs, a strong recommendation, and its flip condition. Not for verifying claims, responding to an ungrounded unknown, or Post.Build.Ship approval and gate policy; use thinking-is-not-knowing or i-dont-know-is-the-answer.