← narwal.one/Second Brain
SecondBrain
Ask the Brain
Index/Conceptupdated Tue Jul 07 2026 08:00:00 GMT+0800 (Philippine Standard Time)

Design Concept (Brooks)

designbrooksshared-understandingai-codingagent-collaborationplanning

Design Concept (Brooks)

Frederick P. Brooks's frame (The Design of Design): when two or more people design something together, they carry a shared invisible idea of the thing being built — the design concept. Not a document, not a spec, not an asset — the ephemeral theory of the artifact that lives between the collaborators. Independently cited by two AI-Engineer 2026 speakers (Pocock and Shihipar) as the missing layer between a human and an AI coding agent.

The claim

  • The design concept exists whether or not it's written down.
  • When two collaborators disagree on what they're building without noticing, the problem is a divergent design concept — not a bad spec, not a bad implementation.
  • Between a human and an AI agent, the design concept is where shared understanding lives — or fails.

Two convergent 2026-07 talks (same conference)

Two speakers at AI Engineer World's Fair 2026 arrived at the same conclusion from opposite directions:

Pocock — from the codebase-quality side

Software Fundamentals Matter More Than Ever (Matt Pocock, AI Engineer): the AI didn't build what you wanted because you and the AI don't share a design concept. Fix: Grill Me — a skill that instructs the agent to interview the human relentlessly, walking down each design tree branch (another Brooks concept), resolving dependencies one by one, until the two sides share an understanding.

"Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one by one."

Grill Me is a 13,000-star viral skill. Ancestor of the interview-me pattern that shows up across the ecosystem (Nate Herk's version, Shihipar's version).

Shihipar — from the model-capability side

Field Guide to Fable (Thariq Shihipar, Anthropic): for Fable-class models the plan/prompt/spec you carry is the map; the codebase is the territory. Places the model runs into territory not in the map are unknowns. Shihipar's Fable-specific practice — "ask Claude to interview me" — is his version of Pocock's Grill Me, aimed at surfacing known unknowns and unknown unknowns before the model starts fanning out.

Shihipar explicitly notes his approach beats Claude Code's default plan mode, which "is extremely eager to create an asset. It really wants to just create a plan and start working." — a tool-side observation that matches Pocock's "specs-to-code is vibe coding by another name."

Why it matters more under AI

The pre-AI form of Brooks's problem: humans disagreeing on the invisible design without noticing. The AI form: the agent has enormous capacity to elaborate any design it thinks it understands, so a divergent design concept produces fluent, plausible, wrong output at speed. The verification bottleneck (Verification Tax) then falls entirely on the human.

Both Pocock and Shihipar prescribe the same intervention: before the agent starts fanning out, interview the human until the invisible design is shared. This is a specific instance of the more general "front-load the alignment cost" pattern.

Related vault concepts

  • Ubiquitous Language — the artifact form of the design concept: the shared vocabulary made explicit. Design concept is the phenomenon; ubiquitous language is one persistent practice for pinning it down.
  • Higher-Order Thinking — Brooks's design concept operates at the higher-order layer (relationships between decisions across the design tree). Producing a design concept is Justin Sung's "mental organization, not physical organization."
  • Skills and Skill Checklist — Grill Me is a skill; the checklist's steering dimension is exactly the class of work needed to build a design-concept-first agent workflow.
  • Specs-to-Code / Spec-Driven Development (SDD) — the movement Pocock is arguing against — treats the spec as if it is the design concept (a writable, versionable asset). Both speakers say this misreads Brooks: the design concept is ephemeral and lives in dialogue, not in a markdown file. The disciplined-SDD framing in Dwarampudi's framework survey partially closes the gap — Grill Me-style interview flows can co-exist with a Constitution + Spec pipeline — but the ephemerality point stands: the spec is one persistence surface for the design concept, not the design concept itself.
  • Verification Tax — divergent design concept is the cause; verification tax is the bill the human pays downstream.

Cross-links

Sources