Adapt your scaled agile ways of working for an agentic SDLC, deciding which coordination mechanisms still earn their keep once agents write much of the code. Inventories the events, boards, roles and gates you run, tests each against the problem it was bought to solve, decides whether human judgment belongs in the flow or on a cadence, and produces one experiment with a leading indicator. Use when adopting agentic engineering, spec-driven development or an AI SDLC raises the question of whether SAFe, LeSS, Nexus or your own scaling apparatus is still needed. Scoped to what an agentic SDLC changes about the cost of coordination — for a scaling framework's own compromises that hardened over time use descaling-experiment-coach, and for the WIP numbers themselves use wip-limit-configuration-coach. If the question is broad — AI pilots with no clear return, or "where do we start" — run ai-activity-to-impact first; it finds the constraint and routes here.