Claude Code Briefing for 28 September: Opus 5.5 capacity, issue closure metrics, concise Opus 5.5 workflows, non-vacuous tests

Claude Code Briefing is a daily audio briefing on the most useful Claude Code workflows, hacks, engineering patterns, design discussions, and best-practice debates from the Claude Code community. This 5-story episode moves through opus five point five capacity, issue closure metrics, concise opus five point five workflows, non-vacuous tests. Chapters 00:00:00 — Intro 00:00:15 — Opus five point five capacity 00:01:55 — issue closure metrics 00:03:21 — concise Opus five point five workflows 00:04:46 — non-vacuous tests 00:06:08 — quota-aware Opus workflows 00:07:24 — Closing 1. Opus five point five capacity The next story is about Opus five point five capacity. Why Claude Code suddenly feels harder to exhaust for some heavy users of Opus five point five. Source link Discussion thread 2. issue closure metrics Next up, issue closure metrics. Tracking whether an agent closes more tasks than it creates can be a sharper workflow metric than asking whether it finished the prompt. Source link Discussion thread 3. concise Opus five point five workflows Then there's concise Opus five point five workflows. Opus five point five is landing as a quality-of-life story, with the poster saying it feels far better than Opus five because the answers are quicker, cleaner, and less bloated. Source link Discussion thread 4. non-vacuous tests Also today, non-vacuous tests. Claude Code tests become useful when they are forced to prove they can fail. Source link Discussion thread 5. quota-aware Opus workflows Finally, quota-aware Opus workflows. Treating Opus five point five as a capacity-management problem starts from a productivity spike on a five x plan. Source link Discussion thread That's your five minutes.