YardMaster and Atlassian Codegeist 202: Building Against the Field

We went into Atlassian Codegeist 2025 (Williams Racing Edition) with our eyes open. The competition was never going to be a student-only hackathon. You are on the same track as agencies and product shops that live inside the Atlassian ecosystem and treat Codegeist as an annual proving ground.

We built anyway. We iterated. We shipped.

What we took home

• 2nd Place — Specialized Industries for YardMaster
• Ranked #1 in India among submissions
• Recognition in Best Rovo Apps (bonus category for apps that put Rovo agents and actions to work on Forge)
• A mention in Atlassian’s winner roundup on the Developer Blog: Meet the Winners of Codegeist 2025

What YardMaster is

YardMaster is about bringing structure and visibility to messy yard and logistics operations. The mental model is simple: act like a race strategist for physical assets — coordinate movements, cut idle time, and keep the operation flowing when plans change.

Technically, that meant leaning into Forge, Jira, and Rovo: turning physical workflows into something teams can see, prioritize, and act on inside tools they already use.

Why this mattered to me

Hackathons are easy to romanticize. This one was a reminder that shipping beats credentials. The leaderboard does not ask whether you are a first-time Forge developer or a marketplace regular — it asks whether your app clears the bar.

If you want the full submission narrative, video, and stack details, the Devpost page is here: YardMaster on Devpost.

Thanks to everyone who reviewed late builds, debated UX in Jira, and kept the scope honest when “one more feature” was tempting.