# Agent Specification Not Code Is the New Bottleneck ## Claim Once a console-based agent builder handles the build step in minutes, the scarce skill in agent development becomes writing a precise specification — a skills file covering mission, capabilities, data sources, and guardrails. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Holds for single-purpose, console-built task agents (analytics, reporting, monitoring) where the build tooling is already mature. - Likely breaks down for multi-agent orchestration or safety-critical systems, where architecture and testing remain the bottleneck regardless of spec quality. - Does not claim the specification writes itself easily — only that it is now the harder and more valuable half of the work, relative to implementation. ## Evidence A live agent-build demo moves from requirements straight into writing a "skills file" (mission, capabilities, data sources, guardrails, acceptance criteria) before any code exists; the presenter calls this file "probably the most critical thing you can think of when building an agent," and the acceptance-criteria items (e.g., filtering bot users) get discovered and written live rather than pre-planned. ## Links - [[3. Resources/Permanent Notes/Context Not Constraints Is What Unhobbles an Agent]] — because extends; both treat what the agent is told (context/spec) as the higher-leverage variable than the model or the code - [[3. Resources/Permanent Notes/A Skills Description Decides Whether Its Used Independent of Instruction Quality]] — because applies-in; a related claim about a different part of the skills-authoring surface (whether a skill triggers, vs. what it should contain) - [[3. Resources/MOCs/AI & the Future of Knowledge Work MOC]] — because applies-in; specification-as-bottleneck is a recurring shift this MOC tracks ## Tests / falsifiers - Time a small cohort building the same task agent: measure time spent on skills-file authorship vs. implementation, across builders with varying tool proficiency — would show whether spec-writing genuinely dominates build time. - Find a case where a thorough skills file still produced a broken or unsafe agent due to implementation/architecture failure, independent of spec quality — would sharpen the scope boundary for multi-agent/safety-critical systems. ## Maintenance - Last tended: 2026-08-16 - Next review: 2026-11-16 ## Source - [[3. Resources/Literature Notes/Zero to Agent in 30 Minutes - Build a YouTube Analytics Agent with Vicki Reyzelman]] — the live skills-file-first build demo this claim generalizes from.