Create a milestone — AI Prompts for GitHub

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 new milestone named Release-1.5 with due date September 30, assign the release manager Ana…

Create a new milestone named Release-1.5 with due date September 30, assign the release manager Ana as owner, and add a short description listing the top three customer-facing items: search speed, token refresh, and mobile layout. Share it with the team channel so everyone knows the deadline.

Improve — make it easier to accept

Before I create the milestone, make it easy to review: surface the candidate issues and their…

Before I create the milestone, make it easy to review: surface the candidate issues and their estimated story points, show which are blocked by external teams, and flag any that lack acceptance criteria so the release manager can decide what to include.

Decide — diagnose the stuck moment

I am setting up Release-1.5 for September 30. Product wants search speed and token refresh; mobile…

I need to create the next milestone but scope keeps creeping.

I am setting up Release-1.5 for September 30. Product wants search speed and token refresh; mobile wants UI tweaks. I am afraid if I include both, the milestone will overcommit and miss the date. What’s the best way to scope this milestone now so we can commit confidently and communicate trade-offs to Ana and product?

Become — change the pattern

Every quarter I create a milestone full of everything stakeholders ask for and we miss the…

Milestones repeatedly get overloaded and miss dates.

Every quarter I create a milestone full of everything stakeholders ask for and we miss the deadline. It wastes planning time and undermines trust. What clear habit or decision rule should I adopt when creating milestones so scope stays realistic and predictable?

Next to this one

Other code hosting work people do in GitHub.

Comment on an issue Commit code changes Compare two branches Configure CI status integration Create a gist Create a new branch Create a new repository Create a PR template Create a project board Create a release

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.

The rest of the map

Same library, five ways in.

Work Atlasthe whole map, interactive Careers1,949 jobs and their real tasks Soft skillsthe human part of the work Activities500 things people do Prompt Librarybrowse every prompt