The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Create a project board in our org acme-corp named Release Q4 2026 for the frontier-ui repo. Include…
Execute — do the immediate task
+Create a project board in our org acme-corp named Release Q4 2026 for the frontier-ui repo. Include columns To do, In progress, Review, Blocked, and Done. Add the open issues tagged release-qa into To do and assign myself as the board admin. Confirm board URL and that issues appear in the To do column.
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 create the Release Q4 2026 project board for frontier-ui, make it easy for reviewers:…
Improve — make it easier to accept
+Before I create the Release Q4 2026 project board for frontier-ui, make it easy for reviewers: suggest column names tuned for front-end work, surface the top five issues by priority to include, flag cross-repo dependencies, and recommend default assignees and automation rules to move PRs into Review when a pull request is opened. Also note any existing boards with overlapping scope.
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 set up a Release Q4 2026 board for frontier-ui and expected issues with the release-qa label to…
Decide — diagnose the stuck moment
+I started a project board but issues didn’t populate
I set up a Release Q4 2026 board for frontier-ui and expected issues with the release-qa label to appear automatically, but the board is empty. I don’t know if labels, repo permissions, or board filters are wrong. What should I check first to diagnose why the issues didn’t show up and how to fix it without rebuilding the board from scratch?
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 create project boards for every sprint but most become stale and people stop updating them,…
Become — change the pattern
+we keep making ad-hoc boards that never get used
We create project boards for every sprint but most become stale and people stop updating them, which undermines planning and credibility. What single change in how we create or maintain boards will make teams actually use them and stop wasting time on abandoned tracking pages?
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 code hosting work people do in GitHub.
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.