lp-executelisted

# LP execution Execute one explicit, reviewed LP intent through a wallet the user controls. 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. For VFAT yield screening, Sickle positions or automation, also read [VFAT guidance](references/vfat.md). ## Start here and connected workflow Before any signature, audit one supplied plan against fresh wallet/chain/pool reads and return a preflight report with each exact missing capability or term. No complete plan means no submission. Receive the exact unsigned plan, its source block, amounts, targets/calldata/value, limits, expiry, simulations and expected effects. If `lp-plan` is absent, use the local [standalone plan intake](references/plan-intake.md) to check a user-supplied plan; do not assume missing planning instructions are installed. Return transaction hashes, receipt blocks/status, reconciled inventory/ownership/allowances, residual funds and unresolved steps to `lp-monitor`. If monitoring is absent, return the same evidence directly for later reconcil