AI代理：撰寫並檢視計畫

dein.fr

Write and checkout the plan

Each AI-aided coding session should start in planning mode. It's become a pretty commonplace recommendation (Boris Cherny, creator of Claude Code, makes this point here). I also recommend checking that plan into the repository.

Summary

Why planning makes sense

Separate your process into two PRs:

The main reason is that it mimics the classical research-design-implement loop.

The first part (the plan) is the RFC. Your reviewers know where they can focus their attention at this stage: the architecture, the technical choices, and naturally their tradeoffs. "It's easier to use an eraser on the drawing board, than a sledgehammer at the construction site"

There are many other reasons why this approach make sense:

Why checking the plan into the repo makes sense

By checking the plan into the (git) repository, you achieve many things at the same time:

What's in a plan

The outline should look something like this:

Tips

Coding agents will increase the momentum towards GitOps

If everything is checked into the repo, coding agents have a much better shot at one-shotting whole projects or features. The more control they have over the end-to-end development workflow, the faster your velocity!

You should consider moving everything into code repositories:

It goes without saying that this doubles as documentation for your team, which will speed up onboarding new engineers.

Resources

Thanks

Thanks to my colleague Sean Koop for providing the inspiration for the practices described in this article.

RSS feedSitemap

© Charles-Axel Dein 2026 - Statically generated with Next.js. Enjoy this cookie-free website!