The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Export the full history for card 8237 on the Product board and for all cards tagged Beta-Test,…
Execute — do the immediate task
+Export the full history for card 8237 on the Product board and for all cards tagged Beta-Test, including every comment, move, field change, attachment add/remove, and automation run with timestamps and actor names. Deliver the export as a single chronological CSV to Compliance and CC me by tomorrow morning.
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 export card histories for Compliance, make their review fast. Produce a single…
Improve — make it easier to accept
+Before I export card histories for Compliance, make their review fast. Produce a single chronological CSV with columns for timestamp, actor, action type, previous value and new value, and card link. Highlight any deletions or attachment removals, and add a brief index at the top showing how many cards and events are included.
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
+Compliance wants full card histories but I’m not confident deletions are tracked the same way as…
Decide — diagnose the stuck moment
+Compliance asked for histories and I’m not sure I captured deletions
Compliance wants full card histories but I’m not confident deletions are tracked the same way as edits. I can export visible changes, but do deleted attachments and comments appear in the export, and if not, what immediate step confirms those deletions are recorded so I don’t mislead Compliance?
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 repeatedly hand Compliance exports that show events but lack context—who approved a change, why…
Become — change the pattern
+History exports always miss crucial context
We repeatedly hand Compliance exports that show events but lack context—who approved a change, why an attachment was removed—so they send follow-ups. I lose time and look sloppy. What recording habit or small metadata field should I add to cards so every significant action has the context Compliance needs without doubling my workload?
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.