# workflow

Al Grigor uses Claude Code as an orchestrator across four roles—product manager, software engineer, QA tester, and on-call engineer. Each task must move from backlog through acceptance before commit, avoiding the trap of one agent writing code and approving its own work.

Anthropic engineer trq212 shares his methodology for coding with Claude Fable 5: the bottleneck isn't model capability anymore—it's whether users can surface their 'unknowns' before, during, and after implementation. Includes prompt examples plus HTML artifacts for visualizing blind spots and plans.

Fable 5 as the commander, Opus as the deep thinker, Sonnet as the grunt worker, Codex as the parallel-universe senior engineer — a multi-model orchestration setup inside Claude Code that reserves the most expensive brain for the most critical decisions.

Kun Chen mapped his daily agent fleet: one "firstmate" managing persistent "secondmates," which spin up disposable "crewmates" per task. Each crewmate gets routed to whichever model is the best deal for the job. gu-log runs its own translation pipeline on the exact same logic.

Most coding-agent best practices from six months ago are now out of date. The new playbook: bigger tasks, longer sessions, and adversarial review so the agent verifies its own work — the engineer just shovels coal into the engine.

Dimillian (an iOS dev now at OpenAI) wrote a field guide for Codex Mobile. The part worth keeping is a mental model that holds across tools: your phone is not a shrunken terminal, it is the control center that keeps you making decisions while the agent does the work.

Matt Pocock's senior-programmer recipe sounds like a joke: install /teach, make a folder, paste a prompt. Underneath is a sharp point: AI is eating tactical coding, so strategic learning now needs durable folders that remember progress.

Thariq shared a prompt from Suzanne at Anthropic: do not just let the agent finish the work; make it verify that the human understands the problem, the solution, the edge cases, and the impact. This is not a teaching fetish. It is about control in the age of agentic coding.

When learning a new tool with Codex, the worst move is asking it to give you a lecture. A better pattern is to ask it for an entry point, a rough map, a tiny exercise, a teach-back check, and breadcrumbs for next time.

Vaibhav Srivastav's Codex prompt is interesting because it describes an agent maintenance loop: look back at recent work, find repeated workflows, and package only high-confidence patterns into Skills, automations, or subagents. It is agent dreaming: turning busy work into capability.

Codex `/goal` is not a wish machine. Chris Hayduk's real point is engineering discipline: give the agent a measurable finish line, a fast feedback loop, and Markdown files that work as long-term memory.

GP-175 covered Opus 4.7 hard specs. This is the workflow layer. Pawel Huryn argues intent is the new unlock. Two-layer CLAUDE.md, per-call effort toggle, batch questions, show-don't-forbid, kill stale scaffolding, review plans not diffs — plus Anthropic/OpenAI converging.

A 25-person agent platform tore down its engineering pipeline and rebuilt it around one idea: agents are the primary builders. Result: 3-8 prod deploys a day, bad features killed same-day, six-week cycles now land in hours. Harness engineering, applied.

Daniel San moved from VSCode to Ghostty, then invented a four-letter mnemonic (SAND = Split / Across / Navigate / Destroy) to burn Ghostty's panel shortcuts into muscle memory. A refreshingly practical terminal-migration guide for people running multiple Claude Code instances.

Paweł Huryn shares three CLAUDE.md instruction blocks—Knowledge Architecture, Decision Journal, and Quality Gate—that turn memory into a self-improving system. After a month, Claude had derived 24 project-specific rules from repeated work.

rodspeed lays out six ways to use Claude Code as general automation, not just a code editor: fresh eyes, meta-skills, freshness-aware search, conversation harvests, structured memory, and handoffs. The deeper pattern is read, filter, decide, present.

Why does Claude perform great in one repo and turn dumb in the next? The answer is the .claude/ folder. Akshay breaks down the full structure: three-level CLAUDE.md, custom commands, agents, permissions, and the global ~/.claude/ you probably didn't know existed.

@daniel_mac8 shares an open-source Elixir implementation: create a Linear issue and move it to 'in progress,' and Symphony picks it up in a dedicated Codex workspace. Codex even writes status updates back. The author argues this is software development moving up an abstraction layer.

A two-person boutique law firm uses Claude to handle the workload of over a dozen associates, from contract review to legal research. Ten years of practice knowledge became Claude Skills, and general-purpose AI outperformed legal vertical tools.

TypeScript guru Matt Pocock: Stop reading AI plans! The real signal is pre-plan conversation quality. If you and AI share mental models, the plan is just a compressed understanding, echoing Brooks' 'design concept' from The Mythical Man-Month.