In my previous post I summarized Anthropic's AI-Native SDLC Playbook , which explains how to redesign the software lifecycle once AI agents can write code faster than your process can absorb it. This post is the practical follow-up: how to actually apply it to a web development project, step by step , with files you can copy into your own repo. Throughout this post I'll use one running example: a Next.js + TypeScript e-commerce app that needs a new "Wishlist" feature. The same steps work for React + Node, Vue, Laravel, Django, or any other web stack. Only the commands change. The workflow at a glance Each stage ends by committing a file, and the next stage starts by reading it: Plan → docs/intent/wishlist.md (what and why) Design → docs/specs/wishlist.md (how) Build → code + tests (guided by CLAUDE.md and Skills) Test → passing tests + CI evals Deploy → PR with AI review findings → human approval → CI/CD Maintain...
AI coding agents like Claude Code can now write code faster than most engineering teams can plan, review, test, or ship it. That speed exposes a problem: our software development lifecycle was designed for a world where writing code was the expensive part. Anthropic's new free course, The AI-Native SDLC Playbook , is a practical guide to redesigning that lifecycle around agents without giving up human accountability. Here's what it covers and why it's worth your time. The problem: the bottleneck moved When agents speed up the build phase, the work doesn't disappear. It piles up somewhere else. The course lists three things that happen: Bottlenecks move to the stages around build: planning, review, and deployment. Manual review stops working. A security team sized for human output either builds a queue or lets code through without a proper review. Governance costs spike. Weekly or monthly exception committees can't keep up with how much agents produce. T...