Agents and AI
I get AI agents working together, with a person in charge.
I split the work into steps, give each agent its own and leave the final say to a human.
Francisco Medrano
I build software with AI and take it all the way to the people who'll use it.
This site is built by a team of AI agents. I decide what goes live.
In progress: story H2 · Home Spec writer
Three things, and they usually go together. AI is little use if the app breaks or nobody ends up using it.
I get AI agents working together, with a person in charge.
I split the work into steps, give each agent its own and leave the final say to a human.
I build the whole application: what you see and what you don't.
Angular on the surface; Java and Python underneath. And tests, so it still works tomorrow.
This site, in Spanish and English, with all its code in the open.
codeOn an Angular application in production, after several version migrations, I redesigned how its library was packaged and recovered most of its tests.
At UC3M I built full stack applications and deployed them from development to production.
I turn what's needed into requirements and coordinate the teams through to delivery.
It's what I do today at INDRA: making sure each team knows what's needed, by when, and what it depends on.
I coordinate the delivery of internal solutions between business areas and multidisciplinary technical teams.
At UC3M I coordinated a development team, from planning to delivery.
This site is run as a project too: Scrum, one spec per page and a public work log.
Reading about it is fine. Trying it is better ↓
Lab
Two demos from my courses that I'm bringing in here, and a third you're already using: this site.
When someone asks to see, correct or delete their personal data, six agent steps prepare the reply. Before it goes out, a person decides.
in progress
A chat built with LangChain and Gemini. It answers as it types and remembers what you've said.
It's built by a team of eight AI agents along the build flow, each with its own role. I'm the Product Owner: I decide what gets built and review what ships. The graph at the top is that team at work.
Spec writer
Writes down, on one page, what each part of the site must do.
Architect
Decides how it's built and writes down why.
Front end
Builds what you see, true to the approved design.
in progressBack end
Builds what you don't see, in Java.
in progressUX/UI
Checks that what was built matches the approved design: screenshots, motion, light and dark.
Test
Checks everything works before it's published.
in progressQA & security
Reviews the work with fresh eyes: it starts from scratch, without having seen how it was coded.
DevOps
Publishes only when the tests pass and I give the go-ahead.
in progressFour habits I bring to every project. This one included.
This site's code, plan and work log are public. You can see what's moving, and what's still missing.
The agents propose and I review. Same with what I build for others: someone always has the final say.
Automated tests and a second review from a clean context before anything goes live.
Much of my work belongs to companies and isn't public. I describe it without client names or internal details, and say where I did it.
Sound like a fit? Let's talk ↓
If your team has an AI idea to design, build or get into the hands of the people who'll use it, tell me about it.
The contact form is on its way. In the meantime, LinkedIn.