An AI that drafts your tasks but is never allowed to create them
My role: Product Manager, Platform and AI. Product, design, backend, AI, two frontend engineers and two QA, across three timezones.
Teams were retyping long briefs and threads into tasks by hand, and losing any trace of why a task existed. I argued against letting the model write straight into the work queue, and drew a line instead: the AI proposes, a person approves, and only then does the platform create anything.
The problem
Teams were turning long briefs and discussion threads into work items by hand. Someone reads the document, decides what needs doing, and retypes it as tasks. It is slow, it comes out differently depending on who did it, and the link back to why a task exists disappears the moment it is created. Weeks later, nobody on the board can answer why something is on it.
My approach
The obvious build is to let the model write straight into the work queue, and I argued against it: that puts something nobody reviewed into the list people are actually working from. So I drew a hard line instead. The AI proposes, a person approves, and only then does the platform create anything. Try to break it below.
Press Push straight to the list and watch what happens. Then try the other one.
Source
brief.md
A long brief, or a thread nobody wants to read twice.
AI proposal · held
proposed, not a task
source: brief.md §3
People decide, then the platform creates
I argued for that shape before the build started. It shipped on the committed date, with ten user stories passing, four blockers and three polish items closed with retest proof, and an independent QA re-test of nineteen items. The go/no-go call itself sat with the product owner.