"AI has eaten tactical programming. It's gone." A snippet from the latest #UnhandledException# podcast episode with @mattpocockuk This bit of the conversation was discussing how, as an industry, we can do technical coding interviews now AI writes all the code.

mattpocock/skills v1.2 is out! We're now the 19th most-starred repo of all time. 13.5m downloads on skills​.sh. Thanks for your support! Here's what's new: - Docs: the community's biggest ask. Every skill documented, with explanations of the main flows + troubleshooting - Claude Plugin: install via Claude's official marketplace - Codex Support: full Codex support via agents/openai.yaml files Updated Skills: - /grilling now asks you questions in rounds, not one-by-one - /prototype now uses HTML instead of a TUI for building logic prototypes - easier to share and far richer - /writing-for-agents renamed from /writing-great-skills, use it for ANYTHING your agents read (AGENTS.md, system prompts, docs) New Skills: - /wizard: tired of provisioning infra? Get your agent to build you a TUI to walk you through it - /to-questionnaire: hit a grilling question you can't answer? Turn the session into a doc you can walk through on a call with a colleague - /wait-what: no idea what the model said? Refocus it in your domain language and simplify with ASD-STE100 Full changelog + docs below. Video soon!

What are you guys using to let your agent spawn other agents? I.e. NOT subagents, but to open more tmux/herdr panes, or claude agents? I have a /claude-handoff skill which I use a LOT, and I'm debating making it into /spawn /spawn would detect what tool you use (tmux/cmux etc) and spawn agents to work on tasks when needed Perfect for /wayfinder

Everyone always confuses my skills with spec-driven-development. It really annoys me. The specs my skills create are intended to be deleted immediately - not kept around, or treated as source code. Birgitta Boeckeler calls this 'spec-first' development, but still groups this under the SDD umbrella (link below). I disagree - I think it needs its own term. The specs aren't that important. They're just a projection of the decisions made during grilling. GDD? Grill-driven-development. IDK

Debating adding emojis to /grilling to make handling batches of questions more readable. You can quickly see the question + recommendation. Much better than trying to squint at a wall of text.

Finally, my skills are available as a Claude Code plugin! claude plugins install mattpocock-skills This means: - No more manually syncing updates - Aliases: mattpocock:code-review means no clashes with Claude built-ins Perfect for folks tired of tinkering. Install once, never worry again.

llm-wiki has been incredibly useful to me personally, but not in code yet. Folks who are doing this, some questions: - Is it checked into the repo? - What stuff goes in there? - When do things get added? (during planning? implementation?) - How do you avoid mismatches?

Someone DM'd me saying they're using /grill-me in technical interviews Watch the candidate work. See how they answer questions and push back. See whether the AI drives them, or they drive the AI. Honestly genius