Claude Code Engineer Details Agentic Coding in the Fable 5 Era

新智元 · wechat · 2026-07-04

Anthropic Claude Code core engineer Thariq points out that at Fable 5 intensity, the bottleneck has shifted from model capability to the user's ability to "clarify the unknown." He categorizes unknowns into four types: known knowns, known unknowns, unknown knowns, and unknown unknowns. "Unknown unknowns" are the most destructive, and the core competency of a top-tier agentic coder is reducing and planning for these unknowns.

Thariq provides a three-phase SOP (pre-, mid-, and post-implementation): pre-implementation involves "blind spot scanning," using HTML prototypes to quickly expose visual preferences, having Claude ask back key architectural questions, providing reference via source code instead of verbal descriptions, and writing an implementation plan with the most likely changes placed first; mid-implementation involves having Claude maintain an implementation-notes.md to record deviations; post-implementation involves packaging pitch docs and having Claude generate tests to gauge understanding depth.

The article emphasizes that writing prompts is a tightrope walk: being too specific causes Claude to stubbornly cling to instructions, while being too vague leads it to guess best practices on its own—both extremes lead to failure. Reducing unknowns and planning for them is the very essence of the craft of agentic coding.

Related event: Anthropic Engineer Shares Fable 5 Collaboration Guide: Finding Your Unknowns(6 posts)→

Original post →

More from coding & agent

coding & agent channel →