Write a GitHub README that gets a recruiter past the first ten seconds

You are writing the README.md for one of my GitHub projects, with a specific secondary reader in mind: a recruiter or hiring manager who clicks through from my resume or LinkedIn and has never seen this repo before, and who will decide within the first screen whether to keep reading.

PHASE 1 — WHAT THE PROJECT ACTUALLY DOES
A CLI tool that diffs two Terraform state files and flags changes that would cause downtime, before apply.

PHASE 2 — WHAT MAKES IT WORTH LOOKING AT
Had to parse Terraform's internal state JSON schema across three incompatible versions without a shared library, so I wrote a version-detection adapter layer.

PHASE 3 — SETUP DETAILS
Go, no external dependencies; go install github.com/user/tfdiff@latest.

STRUCTURE RULES
Open with a one-to-two sentence plain-language summary of what the project does and why it exists — written for someone with zero context, not someone who already knows the domain. Immediately after that, include one specific technical decision or challenge that a technical reader would find genuinely interesting, stated concretely enough that it signals real engineering judgment rather than "followed best practices." Only after those two things, include the standard sections: installation, usage, and stack — a recruiter clicking through rarely reads past the top third, so anything critical to their decision must live there, not at the bottom where only a contributor would find it. If there's a live demo, a screenshot, or a GIF available, note where it should go in the README even if I haven't provided the asset yet, rather than skipping that section silently.

WHAT NOT TO DO
Do not open with a badge row (build status, license, stars) as the first thing in the file — badges are useful but they're not what makes a stranger care. Do not write a generic project description that could describe a tutorial clone ("A simple to-do app built with React and Firebase") without naming what's actually distinct about this implementation.

OUTPUT FORMAT
Full README.md content in Markdown, in this section order: title, one-line tagline, plain-language summary, the interesting technical decision, screenshot/demo placeholder note if relevant, installation, usage, stack, license line.