The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+I need this board’s automation turned off for the sprint cutover. Disable the board-level…
Execute — do the immediate task
+I need this board’s automation turned off for the sprint cutover. Disable the board-level automation rules and confirm by posting a comment on the Sprint Backlog card and notifying Maya in Product. Do not touch global automations. I need confirmation before 5pm Friday so we can make the schema change safely.
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 disable board automation, make it easy for Maya and the team to review what will stop…
Improve — make it easier to accept
+Before I disable board automation, make it easy for Maya and the team to review what will stop running. Produce a short list that calls out which triggers run on card move, which on due date, and any that call webhooks; show likely side effects on the Sprint Backlog and On Hold lists and flag any rule that automates labels or assignments.
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 just turned off the board automation toggle to prevent calls to our webhook, and now the Sprint…
Decide — diagnose the stuck moment
+I flipped the board automation toggle and cards didn’t move as expected
I just turned off the board automation toggle to prevent calls to our webhook, and now the Sprint Backlog cards aren’t moving to In Progress. Maya is watching the deployment and will ask why the workflow stalled. I can’t tell if another rule or a list-specific automation is compensating. What’s the likely cause and the best first check so I can tell Maya what I’ll do next?
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 keep losing deployment windows because someone toggles board automation at the last minute and…
Become — change the pattern
+We routinely forget to disable automations for deploy windows
We keep losing deployment windows because someone toggles board automation at the last minute and breaks handoffs. Across five sprints we had inconsistent behavior when rules overlapped or when webhooks fired during schema changes. Which habit change would most reduce sprint-day friction: a pre-deploy checklist owned by Release, an approvals step on automation toggles, or tagging rules as critical so they require two approvals? Recommend the simplest, fastest policy to adopt.
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.