The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Edit the automation that assigns QA to cards moved to Ready for QA. Change the assignee from Sam to…
Execute — do the immediate task
+Edit the automation that assigns QA to cards moved to Ready for QA. Change the assignee from Sam to Elena, add a 24-hour due date from assignment, and update the comment to read QA assigned: Elena. Verify that existing cards already in Ready for QA are updated and notify Sam by DM that the change is complete.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Improve — make it easier to accept
+Before I edit the QA assignment rule, make it easier for Sam, Elena and Product to accept the…
Improve — make it easier to accept
+Before I edit the QA assignment rule, make it easier for Sam, Elena and Product to accept the change: show how many cards are currently assigned to Sam and how many will switch, surface any downstream rules that fire on assignment (like notifications or checklist templates), and highlight which existing Ready for QA cards will inherit the new 24-hour due date so reviewers can decide if exceptions are needed.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Decide — diagnose the stuck moment
+I edited the Ready for QA rule to assign Elena and add a 24-hour due date, and now a handful of…
Decide — diagnose the stuck moment
+I changed the rule to assign Elena and some tasks lost due dates
I edited the Ready for QA rule to assign Elena and add a 24-hour due date, and now a handful of cards no longer show any due date. Product will ask why deadlines disappeared. I don’t know whether the rule overwrite cleared dates or if another rule removed them after assignment. What is the most likely cause and the immediate rollback or remediation I should run so I can report back confidently?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+We’ve repeatedly edited live automation rules and introduced regressions that break SLAs and…
Become — change the pattern
+We edit rules live and break SLAs
We’ve repeatedly edited live automation rules and introduced regressions that break SLAs and teamwork. Across several edits the common failures are unintended overwrites and missed communications to affected owners. What operational habit should we adopt: versioned rule edits with a dry-run on a staging board, a mandatory notification to assignees before changes, or approving edits in a weekly automation review? Recommend one change and how to pilot it this month.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Next to this one
Other kanban boards work people do in Trello.
Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.
The rest of the map
Same library, five ways in.