ProductivityExample data

Burndown and Gantt

Your Grok Bot team builds you a live Gantt chart and sprint burndown and keeps them current, so you never hand-update a project chart again. A tab per repo, open issues and PRs against the ideal line, milestones with a progress line that bends left when work slips, and the calls that need you this week.

Full-page screenshot of the Burndown and Gantt Page in dark mode
Screenshot of the live Page in dark mode. Open the live Page to use it.

Prompt

Paste into Grok Bot
Make me a Grok Bot Page called "Burndown and Gantt" for my GitHub repos [list them], and keep updating this same Page instead of making a new one. Add a tab per repo plus an "All" tab. For the current sprint (or this week if I have no sprints), draw a burndown curve of open issues and open PRs against an ideal line, with today marked. Under it, a Gantt chart by week of each repo's milestones from start to due date, with a lightning progress line (inazuma line) that bends left for work behind schedule and right for work ahead. Add a table of what each repo must finish this week, with the due date. Put anything that needs me, like a milestone behind schedule or a PR waiting on my review, in a "Needs you" list with a Copy button for each answer. Use GitHub data only and show the time of the last update in my timezone.

Routine prompt (optional)

Keeps the Page updated
Create a routine for my "Burndown and Gantt" Page: every day at 08:00 and 20:00, read open issues, PRs and milestones from my repos on GitHub and update the burndown, the Gantt with its progress line and the table on the same Page. Message me only when a milestone falls more than 2 days behind or a PR has waited on my review for more than a day. Otherwise change only the Page and do not message me.

How to use it

  1. Copy the prompt and paste it into a chat with Grok Bot.
  2. Swap in your own bots, accounts or data sources where the prompt asks for them.
  3. If the prompt does not create a refresh routine, ask Grok Bot for one.
  4. To share your version, make a copy with mock data and make that copy public. Then get it listed.