{"id":57572,"date":"2025-06-26T17:24:06","date_gmt":"2025-06-26T17:24:06","guid":{"rendered":"https:\/\/writer.com\/?post_type=eng_post&#038;p=57572"},"modified":"2026-01-23T12:31:57","modified_gmt":"2026-01-23T12:31:57","slug":"agent-development-lifecycle","status":"publish","type":"eng_post","link":"https:\/\/writer.com\/engineering\/agent-development-lifecycle\/","title":{"rendered":"Anyone can build software now \u2014 and it\u2019s causing hell for developers"},"content":{"rendered":"\n<p data-styleid=\"style-9m7hvqxun\">If you&#8217;re building AI agents in enterprise, you&#8217;ve probably noticed two worlds colliding. Here&#8217;s what&#8217;s happening: business users are spinning up AI agents left and right, feeling like they can build anything. Meanwhile, developers are stuck being the &#8216;reality police&#8217; \u2014 trying to make these things actually work in production while secretly wondering if they&#8217;re automating themselves out of a job.<\/p>\n\n\n\n<p data-styleid=\"style-lhvtihhne\">At the end of the day, many devs feel like they go through all this chaos \u2026 only to end up with a solution not that different from the software they\u2019ve built before.<br><br>From where we sit, however, developers aren\u2019t going anywhere. What\u2019s more, to realize the potential of AI agents, business users and developers need to work hand in hand. So, where do we go from here?<\/p>\n\n\n\n<p data-styleid=\"style-ua3ixpttb\">After deploying over 5,000 agentic systems at leading enterprises like Vanguard, Salesforce, and Uber, we learned some important lessons about what works <strong>AND<\/strong> what doesn\u2019t. As we graduate our <a href=\"https:\/\/writer.com\/blog\/agent-builder\/\">Agent Builder into public beta<\/a>, we\u2019re setting out to create a community of builders who can help us shape a new methodology for the modern enterprise.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-reimagining-the-sdlc-for-an-agentic-world\" data-styleid=\"style-5zq2t50re\">Reimagining the SDLC for an agentic world<\/h2>\n\n\n\n<p data-styleid=\"style-efruhlwit\">In the past two decades, enterprises mastered the software development lifecycle (SDLC). Methods and practices like Agile, DevOps, and DORA brought speed, structure, and predictability to the work of crafting new tools and platforms.<\/p>\n\n\n\n<p data-styleid=\"style-b3pc26drt\">Generative AI threw a curveball into this world, demanding that organizations learn to work with systems that, by their very nature, are non-deterministic. Agentic AI disrupted that playbook further.<\/p>\n\n\n\n<p data-styleid=\"style-c6tu5bfw6\">The tech industry has begun to align around emerging standards like <a href=\"https:\/\/writer.com\/engineering\/mcp-security-considerations\/\">MCP<\/a> and A2A in the last six months. What we don\u2019t have at the moment is a clear methodology for\u200c creating and sustaining these incredibly powerful new tools in enterprise environments.&nbsp;<\/p>\n\n\n\n<p data-styleid=\"style-9m7hvqxun\">What we need is basically &#8216;Agile for Agents&#8217; \u2014 a playbook that actually works for building, shipping, and maintaining agents at scale. Internally we\u2019ve started referring to this as the Agent Development Lifecycle (ADLC.)<\/p>\n\n\n\n<p data-styleid=\"style-7tn9vdqc9\">If you want to help us build the ADLC, sign up here:<\/p>\n\n\n<!--auWTKFVgmi-->\n<div class=\"mwxs:wr-pt-13 wr-pt-13 xl:wr-pt-15 mwxs:wr-pb-13 wr-pb-13 xl:wr-pb-15 \" >\n\n<!--auWTKFVgmi-->\n<div class=\"container-default-sm \" >\n\n<!--auWTKFVgmi-->\n<div class=\"meeting-with-wr-form hbspt-form-theme-1 hbspt-form-important \" >\n\n<!--auWTKFVgmi-->\n<div class=\"prose-h2:wr-fz-7 wr-font-4 prose-h2:wr-fw-medium text-center wr-mb-8 \" >\n\n\n<h2 class=\"wp-block-heading\" id=\"h-join-our-builder-community\" data-styleid=\"style-ngbuyk133\">Join our builder community<\/h2>\n\n\n<\/div>\n\n\n<script charset=\"utf-8\" type=\"text\/javascript\" src=\"\/\/js.hsforms.net\/forms\/embed\/v2.js\"><\/script>\n      <script>\n        hbspt.forms.create({\n          portalId: \"40876074\",\n          formId: \"e0afe2b1-9384-435c-bd8e-9edadba0f2cc\"\n        });\n      <\/script>\n<style>\n.hbspt-form .hs-form-field ul.inputs-list.multi-container li{\n    margin-bottom:10px;\n    margin-left: 3px;\n}\n.hbspt-form .hs-form-field ul.inputs-list.multi-container label:not(.hs-form-booleancheckbox-display) {\n    display: flex!important;\n    column-gap: 13px;\n    align-items: center;\n    color: #7a7a7c !important;\n    font-size: 16px !important;\n    text-transform: none !important;\n    letter-spacing: normal !important;\n}\n\n.hbspt-form-theme-1.hbspt-form-important form .field.hs-form-field.hs-fieldtype-checkbox>label {\n    position: static!important;\n    color: #7a7a7c !important;\n    font-size: 16px !important;\n}\n\n.hbspt-form .hs-form-field ul.inputs-list.multi-container label:not(.hs-form-booleancheckbox-display) > input {\n    width: 15px;\n    height: 15px;\n}\n<\/style>\n\n\n<\/div>\n\n<\/div>\n\n<\/div>\n\n\n<style>\n.hbspt-form-theme-1.hbspt-form-important form .hs-form-field.hs-fieldtype-radio>label{\nleft:0!important;\n}\n\n.hbspt-form .inputs-list.multi-container{\npadding-top: 50px !important;\n}\n<\/style>\n\n\n\n<p data-styleid=\"style-8ouy6tlor\">Over the last few months, we\u2019ve started to put together our perspective on how to address these challenges.&nbsp; We\u2019ve come up with six core principles that form the backbone of our working methodology:<\/p>\n\n\n<figure class=\"expandable-wide-image small_image\">\n            <a href=\"https:\/\/writer.com\/wp-content\/uploads\/2025\/06\/Transforming-the-SDLC-into-the-ADLC-1.png\" data-dcfancybox>\n            <img loading=\"lazy\" decoding=\"async\" width=\"640\" height=\"269\" src=\"https:\/\/writer.com\/wp-content\/uploads\/2025\/06\/Transforming-the-SDLC-into-the-ADLC-1.png\" class=\"attachment-full size-full\" alt=\"Transforming the SDLC into the ADLC\" srcset=\"https:\/\/writer.com\/wp-content\/uploads\/2025\/06\/Transforming-the-SDLC-into-the-ADLC-1.png 1900w, https:\/\/writer.com\/wp-content\/uploads\/2025\/06\/Transforming-the-SDLC-into-the-ADLC-1.png?resize=300,126 300w, https:\/\/writer.com\/wp-content\/uploads\/2025\/06\/Transforming-the-SDLC-into-the-ADLC-1.png?resize=768,323 768w, https:\/\/writer.com\/wp-content\/uploads\/2025\/06\/Transforming-the-SDLC-into-the-ADLC-1.png?resize=1024,431 1024w, https:\/\/writer.com\/wp-content\/uploads\/2025\/06\/Transforming-the-SDLC-into-the-ADLC-1.png?resize=1536,647 1536w\" sizes=\"auto, (max-width: 640px) 100vw, 640px\" \/>            <span class=\"dcfancybox-expand\">\n                <svg width=\"36\" height=\"36\" viewBox=\"0 0 36 36\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n                    <circle cx=\"18\" cy=\"18\" r=\"18\" fill=\"#A8A8A8\" fill-opacity=\".5\" \/>\n                    <path stroke=\"#fff\" stroke-width=\"2.552\"\n                        d=\"M10.72 15.159V8.843M15.787 10.119H9.471M20.842 10.093h6.316M25.882 15.158V8.842M25.909 20.211v6.316M20.842 25.251h6.316M15.787 25.277H9.471M10.747 20.211v6.316\" \/>\n                <\/svg>\n            <\/span>\n        <\/a>\n    \n    <\/figure>\n\n\n\n<p data-styleid=\"style-5mgu85k2r\">Let\u2019s run through these six principles to explain how the SDLC evolves to become the ADLC.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-build-for-outcomes-not-requirements\" data-styleid=\"style-qifex2ukn\">Build for outcomes, not requirements<\/h2>\n\n\n\n<p data-styleid=\"style-kuzhps96p\">In the SDLC, everything was built around requirements: business writes a spec, hands it off, and hopes it holds through dev cycles. In agentic development, it starts with outcomes. That\u2019s a fundamental shift.<\/p>\n\n\n\n<p data-styleid=\"style-rpwpe6486\">The first approach (SDLC) is a mandate in search of a problem. The second approach, ADLC, identifies a problem you can actually solve, measure, and improve. So instead of scoping out a static set of rules, you\u2019re defining what \u201cgood\u201d behavior looks like and designing toward that.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-right-size-solutions-with-agentic-alignment\" data-styleid=\"style-lb0nh0geu\">Right-size solutions with agentic alignment<\/h3>\n\n\n\n<p data-styleid=\"style-33foiv3pl\">The biggest mistake in enterprise AI? Building autonomous agents when you need simple automation. The key is matching the level of autonomy to the actual problem \u2014 not every business process needs an agent that can reason, plan, and act independently. We&#8217;ve learned to start with the minimum viable autonomy \u2014 basic task execution, then structured workflows, then contextual decision-making, and only then full autonomy. Most problems get solved at level one or two.<\/p>\n\n\n<figure class=\"expandable-wide-image small_image\">\n            <a href=\"https:\/\/writer.com\/wp-content\/uploads\/2025\/06\/adlc-2-1.png\" data-dcfancybox>\n            <img loading=\"lazy\" decoding=\"async\" width=\"640\" height=\"360\" src=\"https:\/\/writer.com\/wp-content\/uploads\/2025\/06\/adlc-2-1.png\" class=\"attachment-full size-full\" alt=\"The four levels of agentic systems\" srcset=\"https:\/\/writer.com\/wp-content\/uploads\/2025\/06\/adlc-2-1.png 1400w, https:\/\/writer.com\/wp-content\/uploads\/2025\/06\/adlc-2-1.png?resize=300,169 300w, https:\/\/writer.com\/wp-content\/uploads\/2025\/06\/adlc-2-1.png?resize=768,432 768w, https:\/\/writer.com\/wp-content\/uploads\/2025\/06\/adlc-2-1.png?resize=1024,576 1024w, https:\/\/writer.com\/wp-content\/uploads\/2025\/06\/adlc-2-1.png?resize=950,535 950w\" sizes=\"auto, (max-width: 640px) 100vw, 640px\" \/>            <span class=\"dcfancybox-expand\">\n                <svg width=\"36\" height=\"36\" viewBox=\"0 0 36 36\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n                    <circle cx=\"18\" cy=\"18\" r=\"18\" fill=\"#A8A8A8\" fill-opacity=\".5\" \/>\n                    <path stroke=\"#fff\" stroke-width=\"2.552\"\n                        d=\"M10.72 15.159V8.843M15.787 10.119H9.471M20.842 10.093h6.316M25.882 15.158V8.842M25.909 20.211v6.316M20.842 25.251h6.316M15.787 25.277H9.471M10.747 20.211v6.316\" \/>\n                <\/svg>\n            <\/span>\n        <\/a>\n    \n            <figcaption class=\"figcaption\"><em>Learn more about the four levels of AI agents: <\/em><a href=\"https:\/\/writer.com\/blog\/ai-agents\/\"><em>AI agents in the enterprise<\/em><\/a><\/figcaption>\n    <\/figure>\n\n\n\n<p data-styleid=\"style-naublvqmj\">We recently worked with a customer whose legal team was drowning in contract reviews. They were focused on building \u201can AI legal assistant,\u201d but couldn\u2019t align on what \u201cgood\u201d looked like. They had vague mandates, teams all defined success differently, and the scope kept shifting.&nbsp;&nbsp;<\/p>\n\n\n\n<p data-styleid=\"style-naublvqmj\">We shifted their focus to a clear outcome \u2014 reducing initial contract review time \u2014 and everything else clicked. The behaviors, decision logic, and escalation paths all mapped back to that outcome. And the agent worked.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-put-process-owners-in-the-driver-s-seat\" data-styleid=\"style-3wkxnf710\">Put process owners in the driver\u2019s seat<\/h3>\n\n\n\n<p data-styleid=\"style-0k13b84zw\">The SDLC puts developers and PMs in the driver&#8217;s seat. But with agents? The people who actually know the workflow need to be hands-on from day one. This means it\u2019s essential for <strong>process owners<\/strong> to:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Scope a clear use case with defined outcomes<\/li>\n\n\n\n<li>Map the decision logic and business rules<\/li>\n\n\n\n<li>Validate that the agent aligns to actual workflows<\/li>\n\n\n\n<li>Own feedback loops and signoff for go-live<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-shift-from-process-design-to-behavior-design\" data-styleid=\"style-qegnfgcia\">Shift from process design to behavior design<\/h2>\n\n\n\n<p data-styleid=\"style-1wl2mlsj7\">In the SDLC, you design deterministic processes \u2014 a series of predictable steps, coded against a well-defined spec. Input in, output out. <strong>But with agents, you\u2019re not defining step-by-step logic anymore, you\u2019re shaping agent behavior. That means thinking less about control flow, and more about context and decision-making.<\/strong><\/p>\n\n\n\n<p data-styleid=\"style-1wl2mlsj7\">Success is measured by whether the agent behaves correctly, not whether it followed a static set of rules. <strong>Process mapping is becoming the new prompt engineering. <\/strong>Teams need to rethink (or map for the first time) how work flows throughout their systems, then translate that business logic and scaffold it into a working prototype.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-evolve-from-development-mindset-to-scaling-mindset\" data-styleid=\"style-a19bu39j4\">Evolve from development mindset to scaling mindset<\/h2>\n\n\n\n<p data-styleid=\"style-xbov8pdfe\">A lot of teams today are stuck in development mode. They\u2019re racing to build something that works, focused on one-off use cases. You spin up a new prompt, write new logic, maybe even a new interface, every single time.<\/p>\n\n\n\n<p data-styleid=\"style-05z3r68dw\">It works \u2014 until it doesn\u2019t. Without shared structure, agents will become inconsistent, hard to govern, and impossible to scale. To scale, enterprises need&nbsp; design systems that introduce reusable components and a shared language.<\/p>\n\n\n\n<p data-styleid=\"style-xbov8pdfe\">From there we can build a deep, composable library of prompts, logic, interfaces, and patterns. This empowers&nbsp; teams across the org to turn ideas into prototypes in minutes instead of days. This approach becomes increasingly valuable as companies begin scaling from a handful of agents to hundreds or even thousands spread across different departments.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-move-from-qa-and-testing-to-evals-and-fine-tuning\" data-styleid=\"style-9we9xpe8q\">Move from QA and testing to evals and fine-tuning<\/h2>\n\n\n\n<p data-styleid=\"style-lkq12cons\">In traditional software, QA is objective. You write test cases, check them off a UAT list, and validate whether the code behaves exactly as expected. If it passes, it ships.<\/p>\n\n\n\n<p data-styleid=\"style-f75ljtdv5\">But with agents, behavior emerges in the real world and you only really know how it behaves once it\u2019s out in the wild. And success isn\u2019t binary \u2013 agent behavior doesn\u2019t break in obvious ways.<\/p>\n\n\n\n<p data-styleid=\"style-uudczsl6r\"><strong>&nbsp;It\u2019s not, \u201cdid it break?\u201d But, \u201cdid it behave well enough to be trusted?\u201d<\/strong><\/p>\n\n\n\n<p data-styleid=\"style-lkq12cons\">Testing is more about evaluating outcomes and intent. Instead of pass\/fail, you\u2019re asking:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Does it follow the intended path?<\/li>\n\n\n\n<li>Does fallback logic trigger when it should?<\/li>\n\n\n\n<li>Does it escalate safely when confidence is low or context is unclear?<\/li>\n\n\n\n<li>Does it actually help the user accomplish the task?<\/li>\n<\/ul>\n\n\n\n<p data-styleid=\"style-njf5e3roy\">The goal here isn\u2019t correctness, it\u2019s <strong>behavioral confidence.<\/strong><\/p>\n\n\n\n<p data-styleid=\"style-njf5e3roy\">There\u2019s a lot more room for hyper-personalization of outcomes, too. We were working with a major bank and every unit had a different way they wanted to interact with the agent \u2014 all with the same data, same inputs, same logic. The SDLC would struggle to enable that level of subjectivity.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-break-from-deployment-to-continuous-versioning\" data-styleid=\"style-e8z41y4lt\">Break from deployment to continuous versioning<\/h2>\n\n\n\n<p data-styleid=\"style-n2ab21oem\">The idea of \u201cdone\u201d no longer applies with agents. You\u2019re not shipping once. You\u2019re shaping <em>constantly. <\/em>Because building agents isn\u2019t linear. Agent requirements are ever evolving. Behavior shifts, context changes. Sometimes the smallest change can make a big difference.<\/p>\n\n\n\n<p data-styleid=\"style-mx2fb0r6v\">So you need an MVP mindset \u2014&nbsp; launch fast, monitor closely, iterate continuously. It\u2019s not about launching the perfect agent. It\u2019s about launching them safely, then learning fast and iterating \u2014 over and over again.<\/p>\n\n\n\n<p data-styleid=\"style-9yd1h80t9\">That phrase \u201cbuilding the plane while we fly it\u201d is REAL with agents. And that also means you need a new kind of version control.<\/p>\n\n\n\n<p data-styleid=\"style-n2ab21oem\">Traditional software is versioned at the code level, with mature tooling to support it \u2014 Git commits, branching strategies, pull requests, and CI\/CD pipelines. When something breaks, you can inspect the diff, isolate the issue, roll back the change, and ship a fix.<\/p>\n\n\n\n<p data-styleid=\"style-hhrx2vjlr\">But that model doesn\u2019t map cleanly for agents.<\/p>\n\n\n\n<p data-styleid=\"style-kvlppwwuh\">You can update an LLM prompt and watch the agent behave completely differently \u2014 even though nothing in your git history changed. Model weights shift. Retrieval indexes get updated. Tool APIs evolve. Suddenly, the same input produces a different output \u2014 and you\u2019re left trying to debug a ghost.<\/p>\n\n\n\n<p data-styleid=\"style-hhrx2vjlr\">As we start scaling tens, hundreds, and thousands of agents, version control is essential to control the chaos:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Prompts and system messages<\/li>\n\n\n\n<li>Tool schemas and handlers<\/li>\n\n\n\n<li>Memory configs<\/li>\n\n\n\n<li>Model settings<\/li>\n\n\n\n<li>Full execution traces &#8211; inputs, outputs, reasoning steps, tool calls<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-version-for-behavior-not-code\" data-styleid=\"style-zic3sa1h6\">Version for behavior, not code<\/h2>\n\n\n\n<p data-styleid=\"style-luahe28hh\">Maintenance is a fallacy. With agents, you can\u2019t sit back and watch. In software, observability tells you \u201cwhat happened\u201d \u2013 via logs, errors, and latency. Performance is measured in binary terms. It\u2019s pass or fail.<\/p>\n\n\n\n<p data-styleid=\"style-nok3v139f\"><strong>But it\u2019s not enough for agents.<\/strong><\/p>\n\n\n\n<p data-styleid=\"style-iy5dew7k0\">Escalation logic is missing \u2014 agents either fail silently or alert unpredictably. Lifecycle governance is rarely in place \u2014 agents continue running long after they&#8217;re useful. With agents, we need a new layer of SUPERVISION, one that asks \u201cSHOULD that have happened?\u201d<\/p>\n\n\n\n<p data-styleid=\"style-luahe28hh\">This introduces an entirely new set of primitives to govern agents:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Semantic outcome tracking to evaluate alignment, not just output<\/li>\n\n\n\n<li>Behavioral timelines to audit decisions over time<\/li>\n\n\n\n<li>Confidence thresholds and escalation rules to govern risk<\/li>\n<\/ul>\n\n\n\n<p data-styleid=\"style-a44l122l0\">These new primitives \u2014 semantic tracking, behavioral timelines, confidence governance \u2014 represent a fundamental shift in how we think about software. We&#8217;re not just versioning code anymore. We&#8217;re versioning intelligence, behavior, and decision-making. This requires us to rethink everything we know about building and maintaining systems.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-help-us-imagine-the-future\" data-styleid=\"style-eijdgrd37\">Help us imagine the future<\/h2>\n\n\n\n<p data-styleid=\"style-5zyqrkwd1\">As an industry, we\u2019ve spent the last 30 years mastering software development.&nbsp; We turned software into a well-oiled machine: predictable, structured, and fast to ship. We optimized it to a science \u2014 for deterministic systems.<\/p>\n\n\n\n<p data-styleid=\"style-832prxleh\">But agents aren\u2019t like the deterministic software of the past. And they don\u2019t behave like it. So today, I\u2019m asking you to forget EVERYTHING you know about the SDLC. The tools we have today have completely democratized what it means to build.&nbsp; Now, anyone can prototype an idea in 60 seconds. No Figma, no PMs, no code. The speed of creation is unlike anything we\u2019ve seen before.<\/p>\n\n\n\n<p data-styleid=\"style-5zyqrkwd1\">It\u2019s an INCREDIBLE unlock, but it\u2019s causing hell for developers.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-we-re-testing-our-theory-and-we-need-your-feedback\" data-styleid=\"style-mcxqln401\">We&#8217;re testing our theory and we need your feedback<\/h3>\n\n\n\n<p data-styleid=\"style-7pvhv3nzn\">The reality is \u2014 you can\u2019t build agents the same way you build software. It\u2019s categorically different. Agents don\u2019t follow rules. They\u2019re outcome-driven. They interpret. They adapt. Their behavior only emerges in real-world environments. And the SDLC is breaking under the weight of it.<\/p>\n\n\n\n<p data-styleid=\"style-xtzkknkjm\">Anthony Alcaraz, a senior AI Strategist at Amazon, put it nicely.<\/p>\n\n\n\n<p data-styleid=\"style-n9hs7drrl\"><strong>\u201c<\/strong><strong>The future isn&#8217;t purely probabilistic. It&#8217;s about strategic determinism through structured output. The most successful agent systems I&#8217;ve seen use a hybrid approach:<\/strong><\/p>\n\n\n\n<p data-styleid=\"style-x4ytbv9b1\"><strong>Deterministic infrastructure (schemas, protocols, safety rails)<\/strong><br><strong>Probabilistic intelligence (reasoning, creativity, adaptation)<\/strong><\/p>\n\n\n\n<p data-styleid=\"style-n9hs7drrl\"><strong>Think of it like building a jazz band\u2014you need solid musical structure (deterministic) so musicians can improvise brilliantly (probabilistic).\u201d<\/strong><\/p>\n\n\n\n<p data-styleid=\"style-9tjrhcowq\">If you\u2019re finishing this piece and nodding your head in agreement, we want to hear from you! To make the ADLC a standard that can be widely adopted, it needs validation. Just as DORA metrics proved their worth through public review and testing, we hope to work with partners, customers, and peers to get real data behind the strategies we\u2019re proposing.&nbsp;<\/p>\n\n\n\n<p data-styleid=\"style-7pvhv3nzn\">If you\u2019ve read this far and are shaking your head because you don\u2019t agree with some of the ideas we\u2019ve shared, even better! We need to challenge our assumptions and engage in open debate if we\u2019re going to create something that earns widespread trust.<\/p>\n\n\n\n<p data-styleid=\"style-1fh4ii3lx\">You can read our blog on <a href=\"https:\/\/writer.com\/blog\/agent-builder\/\">Agent Builder<\/a> to learn more about what the platform offers or dive into our docs to learn more about how you can start crafting your first agent today. If you are interested in sharing your feedback on the ADLC, fill out the below form and we\u2019ll be in touch.<\/p>\n\n\n<!--auWTKFVgmi-->\n<div class=\"mwxs:wr-pt-13 wr-pt-13 xl:wr-pt-15 mwxs:wr-pb-13 wr-pb-13 xl:wr-pb-15 \" >\n\n<!--auWTKFVgmi-->\n<div class=\"container-default-sm \" >\n\n<!--auWTKFVgmi-->\n<div class=\"meeting-with-wr-form hbspt-form-theme-1 hbspt-form-important \" >\n\n<!--auWTKFVgmi-->\n<div class=\"prose-h2:wr-fz-7 wr-font-4 prose-h2:wr-fw-medium text-center wr-mb-8 \" >\n\n\n<h2 class=\"wp-block-heading\" id=\"h-join-our-builder-community-0\" data-styleid=\"style-ngbuyk133\">Join our builder community<\/h2>\n\n\n<\/div>\n\n\n<script charset=\"utf-8\" type=\"text\/javascript\" src=\"\/\/js.hsforms.net\/forms\/embed\/v2.js\"><\/script>\n      <script>\n        hbspt.forms.create({\n          portalId: \"40876074\",\n          formId: \"e0afe2b1-9384-435c-bd8e-9edadba0f2cc\"\n        });\n      <\/script>\n<style>\n.hbspt-form .hs-form-field ul.inputs-list.multi-container li{\n    margin-bottom:10px;\n    margin-left: 3px;\n}\n.hbspt-form .hs-form-field ul.inputs-list.multi-container label:not(.hs-form-booleancheckbox-display) {\n    display: flex!important;\n    column-gap: 13px;\n    align-items: center;\n    color: #7a7a7c !important;\n    font-size: 16px !important;\n    text-transform: none !important;\n    letter-spacing: normal !important;\n}\n\n.hbspt-form-theme-1.hbspt-form-important form .field.hs-form-field.hs-fieldtype-checkbox>label {\n    position: static!important;\n    color: #7a7a7c !important;\n    font-size: 16px !important;\n}\n\n.hbspt-form .hs-form-field ul.inputs-list.multi-container label:not(.hs-form-booleancheckbox-display) > input {\n    width: 15px;\n    height: 15px;\n}\n<\/style>\n\n\n<\/div>\n\n<\/div>\n\n<\/div>\n\n\n<p data-styleid=\"style-d60z8uxa7\"><\/p>\n","protected":false},"excerpt":{"rendered":"<p>The SDLC is breaking under AI agents. Learn the 6 principles of Agent Development Lifecycle (ADLC) from teams who&#8217;ve deployed 5,000+ enterprise agents.<\/p>\n","protected":false},"author":1,"featured_media":57812,"comment_status":"closed","ping_status":"closed","template":"","meta":{"content-type":"","inline_featured_image":false,"illustrator_name":"","dc_display_publish_date":true,"footnotes":""},"eng_post_category":[117],"eng_post_tag":[],"class_list":["post-57572","eng_post","type-eng_post","status-publish","has-post-thumbnail","hentry","eng_post_category-thought-leadership"],"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/writer.com\/wp-json\/wp\/v2\/eng_post\/57572","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/writer.com\/wp-json\/wp\/v2\/eng_post"}],"about":[{"href":"https:\/\/writer.com\/wp-json\/wp\/v2\/types\/eng_post"}],"author":[{"embeddable":true,"href":"https:\/\/writer.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/writer.com\/wp-json\/wp\/v2\/comments?post=57572"}],"version-history":[{"count":20,"href":"https:\/\/writer.com\/wp-json\/wp\/v2\/eng_post\/57572\/revisions"}],"predecessor-version":[{"id":63730,"href":"https:\/\/writer.com\/wp-json\/wp\/v2\/eng_post\/57572\/revisions\/63730"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/writer.com\/wp-json\/wp\/v2\/media\/57812"}],"wp:attachment":[{"href":"https:\/\/writer.com\/wp-json\/wp\/v2\/media?parent=57572"}],"wp:term":[{"taxonomy":"eng_post_category","embeddable":true,"href":"https:\/\/writer.com\/wp-json\/wp\/v2\/eng_post_category?post=57572"},{"taxonomy":"eng_post_tag","embeddable":true,"href":"https:\/\/writer.com\/wp-json\/wp\/v2\/eng_post_tag?post=57572"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}