GitHub Labels, Milestones and Project Board Setup
Design a GitHub label taxonomy, milestone plan and project board columns for your team, with naming rules and an issue lifecycle.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Help me organise a GitHub repository so work is easy to find. What the repository is for: [REPO_PURPOSE]. Team size: [TEAM_SIZE]. How we plan work (sprints, kanban, ad hoc): [PLANNING_STYLE]. Current labels and what is messy about them: [CURRENT_LABELS]. Reports we want to pull out: [DESIRED_REPORTS]. Produce: a label taxonomy table with the columns Label, Group (type, priority, area, status), Colour idea, Meaning, Who applies it, with no more than 20 labels and a naming convention such as "type: bug". Next, a rename and merge plan for my current labels, mapping each old label to a new one or marking it for retirement. Then a milestone plan with naming and closing rules, and a project board layout with column names, entry and exit rules for each column, and a work-in-progress limit suggestion. Finish with an issue lifecycle in numbered steps from "opened" to "closed", and a monthly clean-up routine of no more than five checks. Board automation, field types and views differ between GitHub plans and versions, so flag every feature with [VERIFY]. Do not delete or relabel anything automatically; give me a list to review. Do not invent team agreements. If my inputs are thin, ask me up to three questions before writing. Add a worked example with invented figures: 42 open issues, 31 existing labels of which 12 are unused, and show how many labels remain after the merge plan.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.
See an example result (fictional data)
Label | Group | Meaning | Applied by type: bug | type | Something is broken | Triager type: feature | type | New capability requested | Triager priority: high | priority | Fix this sprint | Maintainer area: billing | area | Touches billing code | Author status: needs-info | status | Waiting for reporter | Triager Rename plan: "bug" -> "type: bug"; "Bug!!" -> merge into "type: bug"; "wontfix-maybe" -> retire. Arithmetic with invented numbers: 31 existing labels minus 12 unused = 19 kept. Merging 4 duplicates leaves 15, plus 3 new status labels = 18 labels, within the limit of 20.
Illustrative only, made-up data. Your results will differ and must be reviewed.