Flight Plan
About the author
Hey! I'm Darwin (kidlat-dakila), and I'm glad you stumbled upon this tool! I'm a software engineer based in Munich, Germany, and I'm on a mission to make software engineering fun and enjoyable again in this new AI era.
Just like you, I've struggled to keep up with this agentic coding era, where we push code faster than ever, and I know how hard it is to keep up the pace when we review pull requests. And just like you, I want to keep the coding standard high without sacrificing product velocity. That's why I made Flight Plan.
Why Flight Plan?
My inspiration comes from how pilots fly commercial planes. Did you know that, given proper instructions, it's theoretically possible for anyone to land a commercial plane? Yes, you heard that right! Mentour Pilot has a good YouTube video that shows how: How YOU can land a passenger aircraft! 12 steps.
So if that's the case, why do we need pilots at all? Why do aspiring pilots go through rigorous training, and why is a pilot's license so hard to get? I know you know the answer already. Pilots don't just need to know how to fly the plane. They need to understand the exact parameters that get the plane to its destination safely and efficiently.
Sounds familiar? It's unsettlingly similar to software engineering today. Anyone can vibe-code an app and make it fly. But software engineering is not just about writing code. We deal with trade-offs, scaling issues, maintenance and security.
Built for awesome software engineers just like you!
A commercial pilot doesn't take off without a flight plan, which sets the route, the waypoints and what to expect along the way. Flight Plan gives you that for a pull request. It's an offline-first code review tool that helps you understand and navigate the changes before you read the diff.
- Change Overview
- Every changed code block, sorted by the kind of code it is. See the new page, the components it renders and the state behind them before you open a file.
- Trace Diagram
- How the change runs, from what starts the code through each function it passes to the line you changed.
- Blast Diagram
- Every file the change reaches through its imports, including files the diff never shows.
- Code Walkthrough
- Each changed block of code marked as a waypoint, with a count of the changed files it covers, so you can see what the review left out.
Flight Plan builds all of this on your machine, straight from the code, with no model. Your coding agent adds the why. Setup asks you to pick Claude Code, Codex or Cursor, and when you ask about a line, a code block or the whole review, your agent explains each part right above its code and flags potential bugs. Your code and your reviews stay on your machine.
You're still the pilot. Flight Plan shows you the parameters, so you can keep the bar high and still keep up the pace.
Contact
You can post feature requests in the GitHub repo. I'd like to hear your feedback so I can make Flight Plan better for you! Or contact me on LinkedIn at linkedin.com/in/darwin-talay, and let's keep in touch.