Planning and tracking agent work beyond tickets

Backlinks

Agentic Software — programmeupdated 26 OctWhen agents become the interface, who maintains the software underneath?updated 26 OctStratechery — Ben Thompson’s technology-strategy writingupdated 26 OctTeotti’s AI-first title-software team: evidence into a plan, and a review lesson that did not travelupdated 19 OctA living shared plan is not an acceptance recordupdated 15 OctTalwrn foundation: stable current decisions without treating status as acceptanceupdated 15 OctCodex wiring Datasette traces is not an agent supervision traceupdated 7 OctLinear’s workflow telemetry: more PRs and coordination, not measured requester valueupdated 6 OctVinod Kurien Alex: an agent-driven engineering layer and the missing active-hour ledgerupdated 5 OctStratechery on Meta enterprise: separate contexts or one work-and-life agent?updated 2 OctAnghami Mikrowave: versioned decisions across agents, and bugs after reviewupdated 2 OctParallelPilot: faster ticket coordination did not establish better steeringupdated 2 OctWideSWE: a repository can pass while the feature still failsupdated 2 OctParallel coding agents: coordination, integration and human attentionupdated 2 OctSTALE: clean parallel merges can break a shared invariantupdated 2 OctRole shifts across the agentic software lifecycleupdated 1 OctWhen can an agent close an internal request without a manager?updated 1 OctDo disposable interactive prototypes improve agent-built product decisions?updated 30 SepFaire’s five-PR preview-build tool: planning beyond the ticket, outcome still unmeasuredupdated 30 Seplowtouch.ai’s founder-led rollout: shared deal context and human CRM approvalupdated 30 SepCursor Projects: persistent coordinator across feature, migration and gardeningupdated 28 SepOpenAI Symphony: ticket-level planning replaces session babysitting, not outcome checksupdated 28 SepLinear’s auto-fix boundary is task-shaped: dead flags versus failed background jobsupdated 28 Sep