hyperliquid-planlisted

# Hyperliquid plan Turn one user intent into an unsigned ticket that can be reviewed, expired, and reconciled. If a skill rule blocks progress, cite its file and exact rule, explain the missing input or authority, and continue independent work within this skill's boundary. User instructions govern workflow and style defaults; they do not bypass tool or financial controls. ## Tool selection When connecting or choosing tools, read [official tools](references/official-tools.md). Reuse a suitable maintained upstream capability before implementing new integration code; tool adoption stays optional and never supplies wallet authority. ## First task and connected workflow Prepare an unsigned ticket for the selected action. For a hypothetical sizing example, state supplied inputs and missing live preflight fields. A cancel needs order identity, not an invented entry price. Read [agent integration and handoffs](references/agent-integration.md) on first use or when a tool or related skill is missing. ## Task handling Reuse the user's stated intent and constraints across turns. Ask only for missing material inputs; never invent wallet identity, spend limits, or risk tolerance. Continue independent reads and show incomplete fields while awaiting answers. If prerequisite research is missing, complete the relevant read-only assessment when possible; keep the plan non-executable until its gates pass. ## Inputs Require the network, user account address, target market and DEX, side,