[{"data":1,"prerenderedAt":360},["ShallowReactive",2],{"article-\u002Fblog\u002Fdeath-of-the-13-point-ticket":3},{"id":4,"title":5,"author":6,"body":7,"date":341,"description":342,"extension":343,"featured":344,"logId":345,"meta":346,"navigation":344,"path":349,"published":344,"readingTime":350,"sector":351,"seo":352,"stem":353,"tags":354,"__hash__":359},"blog\u002Fblog\u002Fdeath-of-the-13-point-ticket.md","The Death of the 13-Point Ticket: When Coding Agents Move at Light Speed","RetroAgile Systems Architecture",{"type":8,"value":9,"toc":332},"minimark",[10,14,18,21,24,27,40,43,54,57,62,65,71,74,80,92,96,101,116,130,134,145,149,156,305,309,312,315,328],[11,12,5],"h1",{"id":13},"the-death-of-the-13-point-ticket-when-coding-agents-move-at-light-speed",[15,16,17],"p",{},"For two decades, Scrum sprint planning operated under a single physical constraint: human typing velocity and developer cognitive latency.",[15,19,20],{},"When an engineering team voted on whether a Jira ticket was 3, 5, or 8 story points, they were estimating how long a developer would spend reading legacy code, writing boilerplate, and manually testing edge cases.",[15,22,23],{},"In late 2026, autonomous coding agents severed the link between story points and implementation time.",[15,25,26],{},"An AI coding agent with full workspace access can execute a complex 8-point migration in 180 seconds:",[28,29,30,34,37],"ul",{},[31,32,33],"li",{},"Parsing ASTs across 40 files simultaneously.",[31,35,36],{},"Generating types, updating database migration DDL, and writing regression suites in parallel.",[31,38,39],{},"Opening a pull request before the team finishes their morning stand-up.",[15,41,42],{},"Yet that identical agent, handed a supposedly trivial 1-point ticket with ambiguous acceptance criteria, will spend 3 hours spinning in circular context loops. It edits the same file 14 times, burns through API tokens, and produces a regression that halts CI.",[44,45,51],"pre",{"className":46,"code":48,"language":49,"meta":50},[47],"language-text","[TELEMETRY ANOMALY \u002F\u002F LOG_ID: 984-ALPHA]\nTask: \"Add profile avatar upload, make it fast and secure\"\nPoints Assigned: 1 Story Point (Estimated: 20 min human dev)\nActual Agent Execution:\n- Context Turns: 38 loops\n- Tokens Consumed: 184,200 tokens\n- Files Modified: 12 (7 reverted in thrash)\n- Status: FAILED (Agent assumed local disk storage instead of Cloudflare R2)\n","text","",[52,53,48],"code",{"__ignoreMap":50},[15,55,56],{},"The predictive power of human story points is zero.",[58,59,61],"h2",{"id":60},"the-new-currency-spec-readiness-scoring","The New Currency: Spec-Readiness Scoring",[15,63,64],{},"If human typing speed is no longer the bottleneck, what is?",[15,66,67],{},[68,69,70],"strong",{},"Specification fidelity.",[15,72,73],{},"In an agentic workflow, velocity depends entirely on the clarity of contract boundaries. If a human systems architect provides an unambiguous specification with explicit input\u002Foutput schemas, database constraints, error codes, and test assertions, autonomous agents execute with high first-pass success.",[44,75,78],{"className":76,"code":77,"language":49,"meta":50},[47],"+-------------------------------------------------------------+\n|                 SPEC-READINESS GATE (PRE-FLIGHT)            |\n+-------------------------------------------------------------+\n| 1. HTTP Route & Contract Interface Defined?         [ PASS ]|\n| 2. PostgreSQL Schema Boundary Explicit?             [ PASS ]|\n| 3. Quantitative Error Codes Catalogued (401, 413)?  [ PASS ]|\n| 4. Ambiguous Adjectives (\"fast\", \"secure\") Banned?  [ PASS ]|\n| 5. Deterministic Acceptance Tests Specified?        [ PASS ]|\n+-------------------------------------------------------------+\n| SPEC READINESS SCORE: 98% -> SAFE FOR AUTONOMOUS DISPATCH   |\n+-------------------------------------------------------------+\n",[52,79,77],{"__ignoreMap":50},[15,81,82,83,87,88,91],{},"When you shift planning from ",[84,85,86],"em",{},"\"How many days will this take a developer?\""," to ",[84,89,90],{},"\"Is this spec verifiable for an autonomous agent?\"",", sprint planning transforms from subjective bargaining into systems engineering.",[58,93,95],{"id":94},"_3-core-rules-for-agentic-planning","3 Core Rules for Agentic Planning",[97,98,100],"h3",{"id":99},"_1-ban-ambiguous-adjectives","1. Ban Ambiguous Adjectives",[15,102,103,104,107,108,111,112,115],{},"Adjectives like ",[84,105,106],{},"\"fast\"",", ",[84,109,110],{},"\"scalable\"",", and ",[84,113,114],{},"\"secure\""," cause problems for LLM context windows. They cause probabilistic diffusion—the agent invents defensive caching or arbitrary cryptography that was never requested. Replace adjectives with SLAs:",[28,117,118,124],{},[31,119,120,121],{},"❌ ",[84,122,123],{},"\"Make the endpoint fast.\"",[31,125,126,127],{},"✅ ",[84,128,129],{},"\"p99 latency \u003C 45ms under 500 concurrent requests; cache in Cloudflare KV with 300s TTL.\"",[97,131,133],{"id":132},"_2-lock-schema-first-with-graphpg","2. Lock Schema First with GraphPG",[15,135,136,137,144],{},"Never let an agent guess database columns from ORM abstractions. At RetroAgile, we enforce schema-first development using ",[138,139,143],"a",{"href":140,"rel":141},"https:\u002F\u002Fmihailtd.github.io\u002Fgraphpg\u002F",[142],"nofollow","GraphPG",". The PostgreSQL catalog is introspected natively, creating auto-generated GraphQL SDL and TypeScript types before the feature branch is created. The agent is anchored to a concrete schema contract.",[97,146,148],{"id":147},"_3-acceptance-tests-over-user-stories","3. Acceptance Tests Over User Stories",[15,150,151,152,155],{},"User stories like ",[84,153,154],{},"\"As a user, I want...\""," provide narrative context for humans, but zero verification anchors for autonomous agents. Every ticket must include a deterministic acceptance assertion:",[44,157,161],{"className":158,"code":159,"language":160,"meta":50,"style":50},"language-typescript shiki shiki-themes github-dark-default","\u002F\u002F Deterministic Verification Contract\nit(\"rejects avatar uploads exceeding 5MB with HTTP 413\", async () => {\n  const payload = createMockBuffer(6 * 1024 * 1024);\n  const res = await client.post(\"\u002Fapi\u002Fuser\u002Favatar\", payload);\n  expect(res.status).toBe(413);\n  expect(res.body.error).toBe(\"PAYLOAD_TOO_LARGE\");\n});\n","typescript",[52,162,163,172,202,236,263,282,299],{"__ignoreMap":50},[164,165,168],"span",{"class":166,"line":167},"line",1,[164,169,171],{"class":170},"sH3jZ","\u002F\u002F Deterministic Verification Contract\n",[164,173,175,179,183,187,189,193,196,199],{"class":166,"line":174},2,[164,176,178],{"class":177},"sc3cj","it",[164,180,182],{"class":181},"sZEs4","(",[164,184,186],{"class":185},"s9uIt","\"rejects avatar uploads exceeding 5MB with HTTP 413\"",[164,188,107],{"class":181},[164,190,192],{"class":191},"suJrU","async",[164,194,195],{"class":181}," () ",[164,197,198],{"class":191},"=>",[164,200,201],{"class":181}," {\n",[164,203,205,208,212,215,218,220,223,226,229,231,233],{"class":166,"line":204},3,[164,206,207],{"class":191},"  const",[164,209,211],{"class":210},"sFSAA"," payload",[164,213,214],{"class":191}," =",[164,216,217],{"class":177}," createMockBuffer",[164,219,182],{"class":181},[164,221,222],{"class":210},"6",[164,224,225],{"class":191}," *",[164,227,228],{"class":210}," 1024",[164,230,225],{"class":191},[164,232,228],{"class":210},[164,234,235],{"class":181},");\n",[164,237,239,241,244,246,249,252,255,257,260],{"class":166,"line":238},4,[164,240,207],{"class":191},[164,242,243],{"class":210}," res",[164,245,214],{"class":191},[164,247,248],{"class":191}," await",[164,250,251],{"class":181}," client.",[164,253,254],{"class":177},"post",[164,256,182],{"class":181},[164,258,259],{"class":185},"\"\u002Fapi\u002Fuser\u002Favatar\"",[164,261,262],{"class":181},", payload);\n",[164,264,266,269,272,275,277,280],{"class":166,"line":265},5,[164,267,268],{"class":177},"  expect",[164,270,271],{"class":181},"(res.status).",[164,273,274],{"class":177},"toBe",[164,276,182],{"class":181},[164,278,279],{"class":210},"413",[164,281,235],{"class":181},[164,283,285,287,290,292,294,297],{"class":166,"line":284},6,[164,286,268],{"class":177},[164,288,289],{"class":181},"(res.body.error).",[164,291,274],{"class":177},[164,293,182],{"class":181},[164,295,296],{"class":185},"\"PAYLOAD_TOO_LARGE\"",[164,298,235],{"class":181},[164,300,302],{"class":166,"line":301},7,[164,303,304],{"class":181},"});\n",[58,306,308],{"id":307},"summary-the-architects-role","Summary: The Architect's Role",[15,310,311],{},"Agile is not dead, but the Scrum ritual of planning poker has expired.",[15,313,314],{},"Human software engineers are not typing drones translating Jira tickets into boilerplate. They are systems architects who design specifications, define database boundaries, and review automated telemetry.",[15,316,317,318,322,323,327],{},"Before you dispatch an agent swarm on your codebase, run your tickets through RetroAgile's Spec-Readiness Linter. Pair your contracts with an ",[138,319,321],{"href":320},"\u002Fblog\u002Finternal-developer-platform-for-coding-agents","internal developer platform built for coding agents"," and guard against circular edits by ",[138,324,326],{"href":325},"\u002Fblog\u002Fcontext-churn-and-the-sisyphus-loop","tracking context churn",". Stop estimating points. Start engineering contracts.",[329,330,331],"style",{},"html pre.shiki code .sH3jZ, html code.shiki .sH3jZ{--shiki-default:#8B949E}html pre.shiki code .sc3cj, html code.shiki .sc3cj{--shiki-default:#D2A8FF}html pre.shiki code .sZEs4, html code.shiki .sZEs4{--shiki-default:#E6EDF3}html pre.shiki code .s9uIt, html code.shiki .s9uIt{--shiki-default:#A5D6FF}html pre.shiki code .suJrU, html code.shiki .suJrU{--shiki-default:#FF7B72}html pre.shiki code .sFSAA, html code.shiki .sFSAA{--shiki-default:#79C0FF}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}",{"title":50,"searchDepth":174,"depth":174,"links":333},[334,335,340],{"id":60,"depth":174,"text":61},{"id":94,"depth":174,"text":95,"children":336},[337,338,339],{"id":99,"depth":204,"text":100},{"id":132,"depth":204,"text":133},{"id":147,"depth":204,"text":148},{"id":307,"depth":174,"text":308},"2026-11-05","Why human story points fail in autonomous coding swarms, and how Spec-Readiness Scoring prevents multi-thousand dollar context loops.","md",true,"DISPATCH-001",{"type":347,"canonical":348},"article","https:\u002F\u002Fretroagile.com\u002Fblog\u002Fdeath-of-the-13-point-ticket","\u002Fblog\u002Fdeath-of-the-13-point-ticket","5 min","SPEC_ARCHITECTURE",{"title":5,"description":342},"blog\u002Fdeath-of-the-13-point-ticket",[355,356,357,358],"agile","ai agents","spec-driven planning","scrum reform","6omPwkkOSOKQxgVC_OzagifigUc4LBbiIVd-PP06Td0",1794728603658]