Get the weekly radar
One short email with the freshest products, every week.
Grounded in available product and source data
Our team is small and getting people to update tasks is a hassle so instead we turned it into a clash-of-clans type world. Friday used to be me chasing six people for what they actually shipped, then writing it up for everyone else - now agent roasts people on slack! What it does I type "@quartermaster give DJ the onboarding flow, 30 pts, due Friday" in Slack . Task lands on the board. DJ gets pinged. In front of the team → sets weight: 15, 30, 45 or 60 points. person assigning the work decides what it's worth. You finish it → build catalogue opens at exactly that tier. 15 points buys you a sapling or a lantern. 60 buys a castle gate or a ship. 17 objects across four tiers. You pick your monument and drag it onto a tile. It grows into the world → but it's under construction , gold ring, not real yet. manager approves it → it solidifies, it counts. Or they reject it, and it collapses into rubble . Hover any object in the world → tells you who built it, which task it was, what it was worth. building = receipt. Friday recap isn't written by anyone. The skyline is the recap. 👷 How I built it Stack: Lemma Github repo (Open-source) + Claude (obvs) Time: 2.5 hrs Connected lemma builder skill in claude and described it what I wanted tables/ agents/ functions/ workflows/ surfaces/ apps/ → one command, and the folder became a running system RBAC: lemma Added team roles to it - row-level security, approval workflow, everything The Slack thing isn't an integration I bolted on. surfaces/ is one of the ten folders. The agent in Slack and the agent in the app are the same agent, reading the same tables. You can control agent level access Will be adding the starter kit for this in the github repo itself. submitted by /u/ironmanfromebay [link] [comments]
