Move cards on a project board

Move cards on a project board in GitHub — with the four heights of help laid out: do it now, make it easier for the next person to accept, work out the right move when you are stuck, and learn the pattern so it stops coming back.

4prompt heights
Open it in the interactive atlas →

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 the three cards for Sprint 23 moved to the In Review column before standup. Move the bugfix…
I need the three cards for Sprint 23 moved to the In Review column before standup. Move the bugfix card assigned to Marco, then the dependency update assigned to Sanaa, then the design tasks card assigned to Priya. Verify their labels and assignees stayed intact and post a short comment on each noting the move and that QA has 24 hours to start testing.

Improve — make it easier to accept

+
Before I shift these project cards, make it obvious to reviewers what changed and who should act.…
Before I shift these project cards, make it obvious to reviewers what changed and who should act. Surface the PR number or branch name in the card title, keep the blockers label visible, and add a checklist item showing whether CI passed. Flag any card missing an assignee or a milestone so I can fix them before moving.

Decide — diagnose the stuck moment

+
I just moved a feature card into In Review but it belonged in Blocked; Marcos and QA saw it. I’m…

I dragged the wrong card into In Review

I just moved a feature card into In Review but it belonged in Blocked; Marcos and QA saw it. I’m worried that reviewers will start commenting and waste time. I don’t know if anyone already started QA or who will notice the mistake. Should I move it back and leave a correction comment, notify Marcos directly, or leave it and let the team sort it out? What’s the safest next step to limit wasted effort?

Become — change the pattern

+
Across sprints we keep misplacing cards during frantic planning and then spending hours cleaning…

Cards routinely end up in the wrong column

Across sprints we keep misplacing cards during frantic planning and then spending hours cleaning up. We lose developer focus and create duplicated reviews. Which habit should I change first — stricter column rules at planning, a mandatory one-minute card-check ritual before moving, or assigning a board steward for each sprint to approve moves? Recommend one concrete habit and how to enforce it for the team.

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.