Private circulation Issue 18

Field Notes

A weekly dispatch from the edges of the knowledge graph.

Week of

Aug 17–Aug 23, 2026

15 sources / 65 insights

Five things worth knowing

1
Shahaf Antwarg AI Agents: Orchestration
How I Work With Coding Agents

A workflow synthesis from a developer running 20 parallel coding agent sessions: role shift to tech-lead, isolated worktrees per task, five-part first-message discipline, early direction-checking over end-diff review, manual commits, and a living instructions file.

2
The Startup Ideas Podcast (SIP) 🧃 Claude: Workflow
Treat Claude Code Like an Employee: A 9-Part Operating System

A structured framework for using Claude Code as an 'AI employee' rather than a chatbot, covering repo-as-workspace, memory files (CLAUDE.md/roadmap.md/review.md), plan-mode briefs, scoped tickets, visual verification, three-layer review, scheduled routines, parallel agents, tiered permissions, and reusable skills/hooks — demonstrated via a med-spa missed-lead responder build.

3
Subrouter: Local Proxy for Routing Codex/Claude Traffic Across Multiple Accounts

Subrouter is a Go-based local proxy (manaflow-ai) that distributes Codex and Claude Code traffic across multiple ChatGPT Pro/Claude Max subscriptions and API keys, using sticky conversation-to-account assignment, usage-aware selection, multi-tenant isolation, and optional full-transcript recording.

4
George from 🕹prodmgmt.world Leadership
McKinsey Issue Tree: A Structured Skill for Framing Ambiguous Problems

A PM skill (mckinsey-issue-tree, part of AI PM OS) applies Minto's Pyramid Principle and consulting-style problem trees (Why/What/How) so teams agree on what problem they're solving before jumping to causes, plans, or solutions, using AI to draft branches and run MECE checks repeatably.

5
Harshil Tomar Claude: Workflow
Six tips to sharpen Claude Code sessions

A curated set of Claude Code workflow tricks—sourced from Matt Pacock's skills, Emil Kowalski's micro tips, and personal practice—focused on plan interrogation, TDD enforcement, git safety, terminology consistency, and converting chat into scoped work.