Build Agent Q4 2025: Planning, Figma Integration, and Smarter Troubleshooting

[kristymerri]

https://www.youtube.com/watch?v=FDfa41ot1wk

If you’ve been building with Build Agent since the early days, you’ve probably felt it too: things just work differently now.

With the Q4 2025 release, Build Agent picked up some cool new features... and it’s gotten a lot smarter about how it works alongside you.

Andrew, Patrick and I took a hands-on look at some of these new features in this Creator Toolbox episode, and a few themes really stood out.

---

Build Agent as a Copilot (Not a Replacement)

Patrick summed it up perfectly: you are still the developer. Build Agent is your copilot.

The real magic isn’t just in generating an app with a single prompt (though that’s still pretty cool). It’s in the way you can work iteratively, step by step:

• Ask questions.
• Generate scaffolding.
• Refactor.
• Document.
• Debug.
• Repeat.

Many developers are running multiple Build Agent conversations at once, using it to:

• Understand legacy apps
• Generate documentation
• Create architecture diagrams
• Explore Fluent APIs
• Brainstorm workflows

It’s less about magic and more about friction reduction.

---

The Planning Tool: Keeping the Agent on the Rails

One of the biggest upgrades in Q4 is the Planning Tool.

Before building, Build Agent now:

1. Interprets your requirements
2. Generates a structured plan
3. Asks for approval
4. Then executes step-by-step

So why does this matter in your day-to-day?

Agent-based systems tend to drift in long conversations. The planning tool:

• Refreshes context
• Keeps the agent aligned with original goals
• Reduces debug spirals
• Improves reliability over long runs

It’s a win for both usability and technical stability.

---

Upload Images to Guide Design

You can now drop images right into your Build Agent prompts.

Practical examples:

• Provide a UI mockup for styling inspiration
• Share a screenshot of a broken component
• Reference a visual theme (like a library aesthetic for a book app)

Build Agent takes that visual context and uses it to guide layout and design choices.

It changes the way you approach design and code together on the platform.

---

Figma + MCP: From Design to App

The new MCP (Model Context Protocol) integration opens up something big: agents can now talk to each other.

With Figma MCP configured, you can:

• Paste a Figma design link
• Let Build Agent analyze components
• Generate tables, data models, and UI structure
• Convert design directly into a working ServiceNow app

This goes way beyond styling. Build Agent actually understands the structure of your design.

If you’re on a design-first team, you can now move from concept to a working workflow faster than ever.

---

Understanding Legacy Apps with Mermaid Diagrams

One feature that deserves more attention: auto-generated Mermaid architecture diagrams.

Instead of manually reverse-engineering:

• Tables
• Relationships
• Primary/foreign keys
• Dependencies

Now, you can just ask Build Agent to explain it and create a diagram for you.

This is a game-changer for:

• Onboarding to large projects
• Cleaning up technical debt
• Understanding production systems

---

ATF Troubleshooting Agent

We spend a lot of time talking about building, but testing is just as important.

The new ATF Troubleshooting Agent:

• Diagnoses failing tests
• Provides root-cause insights
• Points to likely fixes

And this is just the start. Future versions may even try to fix issues for you automatically.

It might not be the flashiest update, but it’s one of the most impactful.

---

Why This Matters

Software development is moving faster than ever.

Patrick mentioned something powerful: the way he works today is completely different from a year ago.

Build Agent is right in the middle of that shift.

It:

• Reduces friction for new developers
• Accelerates seasoned developers
• Makes Fluent adoption easier
• Encourages experimentation

And it’s evolving fast.

If you’re using Build Agent today, try:

• Iterative conversations
• Multiple threads
• Architecture analysis
• Documentation generation

Try treating it like a teammate, not just a tool.