Hey, Designer! You find yourself in a BMAD environment?
Before you spiral into existential dread about AI replacing you — hear me out. First of all: know your skills and stay curious. All the logic that goes into this approach is nothing without the emotional human layer a designer will incorporate into a product.
BMAD is, at its core, a framework for making agile less chaotic. It constructs a structured scaffold of information and decisions, delivered exactly where it's needed. And in that kind of environment, designers are in perfect company. They collaborate with people and agents alike, and they deliver what no agent can: opinionated, emotionally resonant design.
There's one real shift worth understanding. In a BMAD team, you're not just designing for users anymore. You're also designing for agents. Your specs, flows, and interaction models feed directly into the pipeline. The Architect, the Developer, the Scrum Master, they all work downstream from you. If your work is clear and structured, it travels. If it isn't, the agents will fill the gaps themselves. (And you know how that looks, eh?)
The fix is simpler than it sounds: build an agent review cycle into your process. Before handoff, run your work through an AI agent and ask it to assess whether the spec is understandable and actionable. Misunderstandings surface fast. You fix them before they compound.
So here's the good news: you still do design. What changes is what comes into your process and what goes out of it. The requirements arrive differently. The handoff looks different. The design itself? That's still yours.