dsh-order-plan

A hotpot dinner falls apart the moment the broth starts rolling and the table descends into chaos: who plunges the shrimp paste first, do the leafy greens go in as a base or later, and who is even in charge of the dipping-sauce station? dsh-order-plan exists to take that coordination burden off your plate. Feed it a set of parameters and it steps back with a sensible serving plan, sequencing which items hit the pot first, which share a round, and which save the show.

Under the hood the tool stays deliberately lean: it runs entirely in Node.js with no network calls whatsoever. There is no API to authenticate against, no external service to reach, and no timeout to chase. In an agent-workflow pipeline it simply registers as a local tool and answers immediately, making it a natural fit for air-gapped environments, internal deployments, or any architecture that treats one less HTTP round-trip as a feature.

Who will actually reach for it? Hosts who gather friends for hotpot on a regular cadence and are tired of improvising the order every time. Developers wiring a chat agent and want a plan-my-hotpot-sequence capability that just works offline. And systems architects who insist that every utility in their toolkit be lightweight, dependency-free, and MIT-licensed. Grab it, call it, walk away.