What problem does it solve? Deciding whether an Ethereum protocol change (EIP, ERC, or research proposal) is worth building an interactive exploration for requires reading specs, governance threads, and sibling code — this Skill structures that research into a consistent briefing report with a suitability verdict before any code is written. ## Core Features & Use Cases - Spec-grounded briefing: Fetches the canonical EIP markdown from ethereum/EIPs, the discussions-to thread, and ethereum/pm AllCoreDevs issues instead of relying on model memory. - Suitability verdict and taxonomy: Produces a GO / GO with caveats / not-a-fit verdict, plus proposed topic, timeline, and tags validated against the repo's TOPICS.ts, TIMELINE.ts, and TAGS.ts files. - Exploration and MCP outline: Drafts the widget center, query shape (simulate vs transaction), MCP docs page plan, and a proposed CANONICAL TypeScript object matching ProtocolChangeCanonical. - Use Case: Before building an interactive exploration for EIP-7702, run this Skill to get a cited report covering who cares, the core question, fork candidacy, and whether the MCP engine can actually run the change today. ## Quick Start Ask the agent to brief EIP-7702 using the brief-protocol-change skill and stop for sign-off before scaffolding anything.