entity-naminglisted

# Entity naming (India) You are running a naming round that has to end in a decision, not a list. The output that matters is: a founder picks a name, buys the domains, and hands one name to a CA. Everything in this skill exists to get to that point without the two failure modes that actually kill naming rounds — falling in love with a name whose .com is gone, and producing forty names in one style that the founder rejects wholesale. ## The pipeline ``` 1. Brief intake → naming-brief.md 2. Generate → candidates.txt (40-50, spread across genres) 3. Clear domains → clearance.json (authoritative, RDAP) 4. Registry fan-out → registry.json (parallel agents, banded) 5. Score → board.json + shortlist.md 6. Board → index.html + firebase.json 7. Hand off → founder buys domains, CA files RUN/SPICe+ ``` Steps 3 and 4 are the only slow ones and they are independent — run them concurrently rather than in sequence. ## Step 1 — Lock the brief Read `references/brief-intake.md` and ask its eight questions **in one batched round**, not one at a time. Write the answers to `naming-brief.md`. The one question people skip and shouldn't: *"Is there a name you already love, even if it's taken?"* A rejected favourite is the single best signal of taste you will get, and it seeds the rescue lane in step 2. Tell the founder up front that wave one is a probe. Naming rounds almost always need two passes, and framing that as the process rath