菜单
The judgment layer for building in the agentic era (Boris Cherny): what to point the machinery at - coding-is-solved, product overhang, build-for-the-next-model, domain > coding, one-week planning, generalist + route-to-specialists, and which moats AI shifts.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Route a task to the least intrusive executive-function support based on the user's stated current capacity, memory load, activation, and motivation. Use when work feels stuck, overwhelming, hard to hold in mind, or when the user asks for neurodivergent-friendly support without wanting a diagnostic or coaching ritual.
Reduce work to the smallest safe and useful outcome when capacity is low or burnout is present. Use when the user explicitly says they are depleted, overwhelmed, unable to start, or asks for the minimum viable version of a task.
Create a truthful activation bridge for a task that has low urgency, novelty, interest, challenge, or immediate feedback. Use when the user says they are stuck or avoiding a known task despite understanding it.
Reduce language, sensory, and uncertainty load while preserving complete information. Use when the user requests direct or scannable communication, has low capacity, is navigating a new flow, or needs explicit expectations and examples.
Turn a vague, oversized, or initiation-resistant outcome into an executable sequence with a visible first action and definition of done. Use when dependencies are hidden, the task spans multiple systems, or the user cannot identify where to begin.
Externalize time, checkpoints, stopping rules, and context transitions. Use when estimates are uncertain, a task may expand indefinitely, the user is switching topics, or an interruption risks losing the current state.
| name | agentic-build-strategy |
| description | The judgment layer for building in the agentic era (Boris Cherny): what to point the machinery at - coding-is-solved, product overhang, build-for-the-next-model, domain > coding, one-week planning, generalist + route-to-specialists, and which moats AI shifts. |
| created | "2026-06-07T00:00:00.000Z" |
| updated | "2026-06-07T00:00:00.000Z" |
| tags | ["strategy","principles","product","moats","planning","judgment","agentic"] |
Not a procedure — the judgment layer that decides what to point loops, agents, and workflows at. Recall when planning what to build, prioritizing, or making a product/strategy call. From Boris Cherny's talk; these are frames, not laws.
agent-fanout).| Power | AI's effect | Your move |
|---|---|---|
| Switching costs | Weaker — the model ports users/data between tools | Don't rely on lock-in; make staying obviously better |
| Process power | Weaker — models hill-climb a process "till it's done" | Expose workflows to agents; keep improving them |
| Network effects | Holds | Collaboration, marketplaces, shared data, distribution loops |
| Scale economies | Holds | Use scale for cost, reliability, trust, speed |
| Cornered resources | Holds | Exclusive data, talent, partnerships, brand, trust |
Software is on the printing-press curve — soon a general literacy, not an engineering specialty, "much faster than 50 years". Startups disrupt 10x more: they build AI-native from zero while incumbents retrain and fight resistance. "Best time to build."
Extracted from Boris Cherny, Why Coding Is Solved (Anthropic, 03:15-17:23), §7 "Strategic frames" + Seven Powers, via the build-catalog extraction. Frames lightly de-disfluencied; not independently fact-checked.