lcp-protocol-spec

To format LCP protocol documentation, update docs/protocol/protocol.md by applying Bolt-style formatting, validating TLV definitions, and ensuring message formats and state flows match upstream Bolt behavior without modification.

TLV definitions in Lightning Compute Protocol specs are Type-Length-Value encoded data structures that define message formats. They ensure compatibility between protocol documentation and the go-lcpd implementation by enforcing consistent semantic rules.

Update LCP protocol specs by editing docs/protocol/protocol.md to reflect the latest definitions, then verify that TLV tables and state diagrams maintain accurate cross-references with the go-lcpd implementation before submitting a pull request.

Yes, the Skill supports maintaining localized protocol-ja.md documentation. It guides editors to update and validate TLV definitions, message formats, and state flows in both protocol.md and protocol-ja.md when applicable.

The primary limitation is that upstream Bolt behavior must remain unchanged. The Skill enforces non-modification of upstream Bolt logic while allowing edits to TLV semantics, formatting, and LCP-specific state flow documentation.

Yes, you can use this Skill to validate state diagrams and message formats for LCP v0.2. It guides editors to verify TLV tables and update docs/protocol/protocol.md to reflect the latest LCP v0.2 definitions accurately.