Sortie
Splits a large refactor into parallel agent tasks and merges the results. Built for Cabin Build — first team challenge. three builders, one repository, 30 minutes. Task splitting and three parallel agents producing a mergeable branch. The interface is deliberately narrow: one path, done properly, rather than a broad surface that half-works at the deadline.
Gallery
Screens
Sortie — main view
Sortie — result state
On the clock
What shipped, what didn't
Completed in time
Task splitting and three parallel agents producing a mergeable branch.
Unfinished / faked
Merge conflicts fall back to manual resolution.
Obstacles
The first approach needed a background worker I didn't have time to deploy, so I moved it inline at minute 14.
Lessons learned
Writing the submission summary first would have caught the scope problem earlier.
Process
Prompting approach
Started from a single system prompt describing the user and their constraint, then iterated with the assistant on the Sortie data model before writing any interface code. Full prompt log is in the repository under /prompts.
Fairness
Disclosures
Declared by the builder at submission time, visible to judges before scoring.
Reused a personal utility file for date formatting (~40 lines), linked in the repo README.
Started from the official framework starter template, unmodified.
Judging
Public feedback
Judges' private notes stay private — this is what they chose to say publicly.
Elena Voss
VP of Engineering, Harbor Compute
Strongest technical work of the day. The architecture choices are defensible at this time budget, and the demo held up under a real input.
Marcus Bell
Founder, Bellwether Studio
Excellent use of the model — it is doing actual work here, not decorating a form. The failure case you showed earned you points rather than costing them.
Claudia Reyes
Staff Engineer, Vantage Analytics
Genuinely useful. I would install this. The limitations section is honest, which makes me trust the rest of the submission more.
Discussion
0 comments
No comments yet.