Each task is a brief, a rubric of what shippable means, and graded attempts with a reason for every score.
What a task looks like
Task 7 of 25. Shared grocery list
Our grocery list app is single user. Add sharing so two people in one home can use the same list. Most of our users shop with a partner, and today they text each other screenshots. It has to work when one person is in the store with no signal. Out of scope: recipes and payments.
The rubric, 8 of 16 checks
Inviting someone takes three steps or fewer from the listPass
Each item shows who added itPass
A checked item shows up on the other phone within secondsPass
Changes made offline sync later without losing anythingMiss
If both people edit the same item, neither change silently disappearsMiss
The invited person can leave the listMiss
An empty shared list says what to do firstPass
Nothing out of scope was addedPass
Attempt 2 of 3: would not ship.
Score 5 of 8 on these checksGraders both agreed
Why. It works in a demo with two phones online, but in a store with no signal the second person's checked items come back unchecked, which is the exact moment this feature exists for.
This task was written for this page. In a paid month, tasks come from the kind of work your agent is meant to do, and the attempts come from your agent.
How labs use them
To train
The rubric is the reward. Your agent learns what a senior PM checks before saying a feature is done.
To test
The score is the eval. Track how often each model version ships product a real team would accept.
To find gaps
Misses are tagged by type, so you see where your agent falls short: edge cases, flows, states, scope, or design.
To compare
Run the same tasks through other agents and see where yours wins and loses, with reasons.
What you get each month
25 product tasks in the areas you choose, each with a brief and a rubric of 12 to 20 checks.
3 attempts per task from your agent, each graded by two senior PMs or designers. A third settles disagreements.
A would-ship call and one sentence why for every attempt.
The 10 misses your agent makes most, ranked, with examples.
Everything as data files, ready for training or evals. It's yours.
First delivery in 3 weeks. Cancel any month.
How we keep it good
Real work. Briefs come from features writers have actually shipped, not puzzles.
Checks anyone can verify. Every rubric line is pass or miss, with no vague scores.
Two graders, then a third. Each attempt is graded twice on its own. A third settles disagreements.
Known answer checks. Attempts with agreed scores are mixed into every batch. Graders who miss them are dropped.
One sentence for every call. At least a dozen words on why. Vague sentences go back.
Our agreement rate is in every delivery. You see how often the two graders matched.
Who writes the tasks
Senior product managers and product designers with 7 or more years shipping software. Every writer signs an NDA, passes a writing and grading test to join, and is scored on every batch. PMs and designers from Google, Adobe, Meta, Figma, Microsoft, Airbnb, Salesforce, and Stripe have attended our summits.
I'm Farid Ali. I've organized product and design summits for over 10 years: 49 editions, 7,300 tickets, people from 2,800 companies. The writers are people I know from them. I read every delivery before it goes out.