The video argues that a year of Claude Code advice is now outdated because the newer models (Opus 5/5.5) handle planning, self-checking and delegation on their own. Boris Cherny, who built plan mode, reportedly said on Hacker News that it's no longer useful; the replacement is a short brief with task, guardrails and a definition of done, then checking the output afterwards. The rest is a cleanup list: drop 'think hard' prompts for effort levels, turn done-criteria into runnable checks plus /goal loops, shrink CLAUDE.md to an index of pointers, build skills only from observed failures, replace shouty rules with hooks, and let Claude spin up its own subagents within caps.
- Plan mode was just a reminder injected into prompts to stop older models coding immediately; with newer models planning happens while they work, so the recommended replacement is a three-line brief (task, guardrails, definition of done) plus asking for a diagram or one-page visual of what the model did and assumed.
- Prompt phrases like 'think hard' and 'ultrathink' are now read as ordinary words — thinking budget is a separate effort-level setting, and Anthropic says Opus 5.5 on medium matches or beats Opus 5 on high, so leave it on the recommended level.
- Giving Claude a way to verify its own work is claimed to 2-3x output quality; instead of saying 'double check your work' (which the model does anyway), turn the definition of done into a pass/fail check — a script, or even a brand voice doc the draft is compared against.
- /goal automates typing 'continue', but the judge is a small separate model (e.g. Haiku) that only sees the chat and Claude's output, not files or commands — so a vague goal like 'the report is finished' will complete prematurely. A good goal states one end state, how to prove it, what mustn't change, and a turn limit.
- Anthropic deleted over 80% of Claude's own instructions when Opus 5 shipped because most were fixing old-model mistakes; CLAUDE.md should stay under 200 lines and act as a contents page holding only tools Claude can't guess, your deviations, repeat gotchas and hard boundaries.
- Pointers in CLAUDE.md should be file paths with a trigger condition, not @imports (which load the whole file every session); every file should be linked directly from CLAUDE.md because nested files only get their first 100 lines previewed, and files over 100 lines should start with a contents list. /doctor prompt-audit can do this cleanup for you.
- Skills should be built backwards from failure: run the task with no skill, note only the corrections needed, and test on the model you'll actually use. Anthropic's own best skills started as a few lines and a single gotcha.
- A developer's test of nine popular skill packs — 450 runs on Opus 5.5 — found only two beat a dummy file of the same length; use /skill-doctor and the plugin eval (skill vs no skill) to delete skills that are just costing tokens.
- Rules written in capitals should either be deleted (Claude does it anyway) or converted into hooks — deterministic scripts that run at defined moments, use no tokens, and cannot be ignored.
- Claude now delegates to subagents more readily than any prior model, so the user's job is setting caps and boundaries rather than hand-building agent teams — except inside skills, where heavy research or MCP steps should be explicitly pushed into a subagent to keep the main context clean.
- Projects are now one ongoing conversation that spawns its own threads and keeps running when your machine is off, which combined with scheduled or event-triggered tasks lets routines run unattended.
What replaces plan mode
0:50–1:56
It's the core claim of the video — the concrete three-part brief format that replaces upfront planning, with a worked example.
He describes the task, describes the guardrails that surround the task, describes what done looks like... and then lets the model actually work it out.
The /goal judge can't read your files
5:12–6:06
A non-obvious failure mode that causes loops to stop early, with the exact fix for how to word a goal.
The catch here is that the judge, i.e. that Haiku agent, doesn't run commands or read files independently. So it only gets given the chat that you sent it and Claude's output.
In January, Boris Cherny said most of his sessions start in plan mode. But two weeks ago on Hacker News, he said plan mode is no longer useful.
Leave Claude alone doing its thing until it makes mistakes, then add the infrastructure and files like skills to give it some support.
If the two scores come out the same, then the skill is just costing you more tokens — i.e. it's just decoration.