lp-engineerlisted

# LP engineer Build protocol-aware LP software with deterministic plans, explicit signer boundaries, and receipt-based truth. 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 Identify one concrete missing capability or adapter defect, define its input/output and failure contract, then run a read-only fixture or inspect a test that demonstrates it. Installation alone is not evidence that an integration exists. Receive the readiness gap from `lp-setup` or equivalent actual tool inventory, chain/protocol, required methods and failed evidence. Return implemented capability, installation/configuration instructions without secrets, exact tests, unsupported paths and a read-only verification procedure to `lp-setup`. If it is absent, perform and report that procedure directly. Keep analysis, planning, execution and monitoring interfaces explicit even when their skills a