---
title: "I want AI to make me a Gantt chart"
url: https://iwantaito.com/asks/make-me-a-gantt-chart/
summary: "Five plain-English prompts made a one-file project plan: tasks as bars on a calendar, sections, tasks that wait, tick-boxes, save to a file. No account. Upload to GitHub; Cloudflare hosts it free."
published: 2026-10-09
updated: 2026-10-09
author: "Jack Stovell"
publisher: "Adapt Progress Evolve Limited"
language: en-GB
---

# I want AI to make me a Gantt chart

Five plain-English prompts made a one-file project plan: tasks as bars on a calendar, sections, tasks that wait, tick-boxes, save to a file. No account. Upload to GitHub; Cloudflare hosts it free.

> Village Summer Fete 2027: Made up for this demo. The fete, its date and the helpers' first names are invented: we typed the organiser's side into the prompts, and Claude wrote the 17 example tasks and the six names itself.

Run: 2026-10-09, claude-sonnet-5-5, Claude Code 2.1.293 (claude -p, file tools only: no terminal, no web), session bffa090c-6925-4960-bca3-29f8d19548af. Claude's time: 10 min 58 s. Edited by hand: no. Full transcript: https://iwantaito.com/transcripts/make-me-a-gantt-chart.md

## Set up once

Step by step, with what each screen looks like: https://iwantaito.com/start/

1. **Get a free Claude account**. It's where you describe what you want and Claude makes it. The Free plan covers every guide on this site; for websites, Pro adds the shortcut where Claude saves changes to GitHub itself. Free (Pro is optional).
2. **Let Claude hand you files**. Everything on this site is a handful of files: a website, an app, an extension. With this switched on, Claude can make them and give them to you to download. Free.
3. **Get a free GitHub account and an empty repository**. A repository is a folder on GitHub that keeps every version of your files. It's the one place your site lives: you (or Claude) change the files there, and Cloudflare publishes whatever is in it. Free.
4. **Get a free Cloudflare account and connect it to your repository**. Cloudflare is where your site is live on the internet. Once it is connected to your repository, every change to the files on GitHub goes live by itself, in a minute or two. A site made of plain files costs nothing to host: Cloudflare says requests to static files are "free and unlimited". Free.
5. **Connect Claude to GitHub**. So Claude can read the files that are live now before it changes them, even in a brand new chat. On Pro, the same connection is what lets Claude Code on the web save its changes to your repository. Free.

## The prompts

### Prompt 1 of 5: Describe the chart you want, and ask Claude to ask questions first.

```text
I'm organising our village summer fete and I'd like a project plan chart, the kind with bars across a calendar showing what has to happen and when (I think they're called Gantt charts). I've never made one, I'm not technical, and spreadsheets confuse me. I'd like to use it in a web browser on my laptop and look at it on my phone.

What I'd like:
- a list of tasks, each with a start date, an end date and who is doing it
- the tasks drawn as bars on a timeline so I can see what overlaps and what's coming up next
- a way to tick tasks off as done
- it should remember my plan when I close it and come back, with no account and no sign-in
- it should be free to run

Before you make anything, ask me anything you need to know, and tell me in plain English what you're going to make.
```

What you should see: A plan and some questions, and nothing made yet. Ours promised one file with a task list, bars on a timeline, tick-boxes and a plan remembered in the browser.

### Prompt 2 of 5: Answer its questions and ask it to make the chart.

```text
Thanks, that sounds right. My answers:

- The fete is on Saturday 11 September 2027 and we've got about ten weeks. Please start the plan on Monday 5 July 2027 and make up about 15 realistic tasks for a village fete (booking the hall field, stalls, insurance, posters, raffle prizes, first aid, setting up, clear-up and so on), with made-up first names for who's doing them, and I'll change them to ours.
- Bars coloured by person, with today's date marked, and done tasks shown differently.
- I'd like to add, change and delete tasks, and I need to be able to see the whole ten weeks without scrolling sideways on a phone, or scroll if it has to.
- Yes to a way to print it on one page, and a way to save my plan to a file and load it back so I can move it to another device.
- A clear, calm look with big readable writing.

Please make it now. Keep it as simple as possible: something I can open by double-clicking and later put online, nothing I have to install.
```

What you should see: One file to download. Ours: fete-plan.html, with ten weeks of bars coloured by person, 17 made-up tasks, a marked fete day and Save to file and Load from file buttons. Claude said it had not opened it in a browser.

### Prompt 3 of 5: Ask it to check the dates, the phone and the print, and fix it.

```text
I opened it by double-clicking and had a play. Before I share it with the committee, please check it carefully, as if you were me on a small phone, and as if you were trying to find mistakes: every button should do what it says, the bars should sit on exactly the right dates (a task that ends on a Friday should end on that Friday), a task whose end date is before its start date should be handled sensibly, ticking tasks off and the plan should still be there tomorrow, and saving then loading the plan file should bring everything back. Also look for writing that's too small or too faint, anything that spills off the side of the screen, how it prints, and anything that would trouble someone who uses a screen reader or only a keyboard.

Tell me in plain English what you found, then fix it in the file.
```

What you should see: A plain-English list of fixes and the file updated. Ours fixed week labels cut off on a phone, a bar sticking out past the edge, a printout that would spill onto a second page, and a typo year stretching the calendar, and said it had read the code, not run it.

### Prompt 4 of 5: Change something, the way you will once it is live.

```text
Thank you, it's working well. The committee has asked for two changes. First, I'd like to group the tasks into sections (like "Before the day", "On the day" and "Afterwards") so the chart is easier to read. Second, some tasks can't start until another one has finished, like "print posters" can't start until "agree poster design" is done, so I'd like to say that a task comes after another one and have the chart show it.

I've already put my own tasks in, so they mustn't disappear when I put the new version online. If they don't have a section yet, that's fine.

Then tell me which files you changed, so I know what to put online again.
```

What you should see: Sections and a 'comes after' setting, and a note that only fete-plan.html changed. Ours added section headings with a count, a dashed line for a task that has to wait, and red marks if the dates don't fit, and said to Save to file before uploading.

### Prompt 5 of 5: Ask how to put it live from GitHub, and whether the committee will see the same plan.

```text
Now I'd like to put it online so the committee can open it on their phones. I've made free GitHub and Cloudflare accounts. On GitHub I made a new repository called village-fete-plan (I switched on "Add README"), and in Cloudflare I went to Workers & Pages, Create application, Pages, Connect to Git, and picked that repository, so it should go live by itself whenever the files on GitHub change. I don't want to use the terminal or install anything.

Please tell me, step by step, how to get the chart into my repository using the GitHub website, what I should see at each step, how I find the address where it's live, and how I put a change live later. Also tell me honestly whether the committee will all see the same plan when they open the link, or each their own.
```

What you should see: It made a copy named index.html for us, then gave click-by-click steps. Ours said no: everyone gets the same page, but each person's plan stays in their own browser, and you share a plan by sending the saved file.

## Before you start

You need three free accounts and nothing else. A Claude account with "Code execution and file creation" switched on (Settings, then Capabilities; it's on the Free plan), so Claude can hand you a file to download. A GitHub account with an empty repository, where the file will live. And a Cloudflare account connected to that repository, which puts it on the internet. [The set-up page](/start/) walks through all three, once.

Nothing to install, and no terminal. Everything below happens in a chat and a web browser.

Our example is a made-up organiser of a village summer fete, on Saturday 11 September 2027, with about ten weeks to go. They want a project plan chart, the kind with bars across a calendar, and they've never made one. Spreadsheets confuse them. They want to use it on a laptop and look at it on a phone, with no account. The fete, the tasks and the helpers' first names are all made up. Swap in your own event.

## What happened when we ran it

We typed five plain-English prompts into one conversation with claude-sonnet-5-5 on 9 October 2026. We ran them through Anthropic's command-line tool with only its file tools switched on, much like file creation on claude.ai, so your screen will look different. The replies are published as they came back and we edited nothing by hand. Claude spent 657.5 seconds writing them, a little under 11 minutes.

The first prompt made nothing. Claude answered with a plan and some questions. In prompt 2 we answered: the date, 15 or so made-up tasks, bars coloured by person, today's date marked, and a way to save the plan to a file. Claude saved one file, fete-plan.html, with 17 example tasks and six made-up names, and said it hadn't opened it in a browser.

We tested it in a browser, with the clock set to 20 July 2027 so that "today" was on the chart. The first build passed 54 of 60 checks. The bars were right: all 17 started and ended on the dates written beside them. But it printed on two pages, not one, the smallest text was 13.68 pixels, and the buttons on a phone were small.

Prompt 3 asked Claude to check the dates, the phone and the print like a user, hunting for mistakes. It said it could only read the code. It still fixed a long list: week labels cut off on a phone, a bar on the last day sticking out past the edge, "Today" and "Fete day" tags that overlapped, a printout that spilled onto a second page, and a typo year such as 2072 that would have stretched the calendar. It now asks "Is the year right?". After that the plan printed on one A4 page.

Prompt 4 asked for sections and for a task to come after another, and said our tasks mustn't disappear. Claude added section headings with a count ("2 of 15 done"), a "Can't start until this task has finished" list, and a dashed line with an arrow in the waiting task's row. If the dates don't fit, the task gets a red outline. We tested it: moving the earlier task later marked the later one in red, and "before the day" typed in lower case joined the existing section. The final file passed 70 of 74 checks.

The four misses are all on a phone, and none stops it working. The section headings, which are buttons that rename the section, are 27 pixels tall, and two footer buttons are 42 (we look for 44). The chart is 4 pixels wider than its box. And a one-day task on the last day is drawn a little wider than its day, because Claude draws every bar at least 7 pixels wide.

Not everything is as you'd guess. Choosing the task a new one has to wait for doesn't move the start date; it only warns you if you save it too early. And we didn't test a real printer, a real phone or a screen reader.

## Put it live

Prompt 5 was the nicest surprise: Claude made a copy of the file called index.html itself, so there was nothing to rename. These clicks follow GitHub's and Cloudflare's documentation and Claude's answer. Claude's unedited file is live at [demo.iwantaito.com/make-me-a-gantt-chart/](https://demo.iwantaito.com/make-me-a-gantt-chart/) (we host it ourselves, with a thin bar on top saying it's a made-up example).

1. If you've already added your own tasks, open that copy first and select Save to file. Your plan lives in that browser, and the online address starts with the example plan.
2. Download the file Claude made, index.html. Upload only that one, not fete-plan.html.
3. On GitHub, open your repository and select Add file, then Upload files. Drag index.html in, or select "choose your files". Select Commit changes. The repository now lists README.md and index.html.
4. If you left Cloudflare's setup screen open, check the production branch is main, the framework preset is None and the build command is blank, then select Save and Deploy. If you'd already finished it, your upload starts a new deployment by itself.
5. In Cloudflare, open Workers & Pages, then your project. Under Deployments, wait for the newest one to say Success. The address ends .pages.dev, such as village-fete-plan.pages.dev. Open it: you should see the example plan.
6. To put your own plan on it, open the live address, select Load from file and pick the file you saved in step 1.
7. To put a change live later, ask Claude in the same chat, download the new index.html and upload it the same way. A file with the same name replaces the old one.

Will the committee all see the same plan? No. Everyone gets the same page, with the example plan, and each person's changes stay in their own browser on their own device. Your real plan is never uploaded. To share it, send them your saved file and they select Load from file. A single live plan for everyone would need a small online database behind the page. Claude also offered to open with a blank plan instead of the example.

## What it costs

£0. Claude's Free plan covered all five prompts, GitHub's Free plan holds the file, and Cloudflare says "Requests to static assets are free and unlimited". The whole chart is one file of 38,829 bytes, and you don't need a domain.

The catches aren't about money. Each device and each address keeps its own plan, and saved plans are lost if you clear your browser's data or use a private window. Use Save to file now and then as a backup.

If you want a plan everyone can edit at once, the next step up is a shared app that saves to a database. We built [a database-backed app](/asks/build-me-an-app/) with five plain-English prompts: a shared job list for a community garden. You upload two files to GitHub, Cloudflare puts it live, and it's free, with no terminal.

## What we tested

- PASS: Final file (prompt 5), opened by double-click, with the clock set to 20 July 2027 and real clicks, taps and typing at laptop (1440x900) and phone (390x844) size in headless Chrome. 70 of 74 checks passed: no errors, nothing loaded from other websites, the whole ten weeks fit across a phone, no sideways scrolling of the page, text contrast fine. The 4 misses are on the phone: see "Small things on a phone" below
- PASS: Bars on the right dates. Every bar (17 in the first build, 18 in the last) started and ended on the dates written beside them, at laptop and phone size (apart from a one-day task on the last day, which Claude draws at least 7 pixels wide). A task added for 10 to 13 August landed on those dates, and moved when its end became 20 August
- PASS: Ticks, adding, saving and loading. A ticked task, an added task and an end-before-start refusal all behaved. Save to file, then Start again, then Load from file brought back all 19 tasks and the tick; a file that was not a plan was refused
- PASS: Sections and "comes after". Section headings showed counts ("2 of 15 done"), and "before the day" typed in lower case joined the existing section. A task that comes after another showed a dashed line and "comes after" wording. Moving the earlier task later marked the later one in red, and the form did not offer a task as coming after itself
- PASS: Printing. In print layout the buttons were hidden and the example plan came to one A4 landscape page. The first build came to two pages
- FAIL: Phone details. Section headings (which rename the section) are 27 pixels tall and Start again and Put back the example are 42 (we look for 44); the chart is 4 pixels wider than its box; and the last one-day bar is drawn 1.45 days wide
- FAIL: A real printer, a real phone (including loading a file on one) and a screen reader. Not tested

## What it got wrong

- **Printed on two pages at first.** In the first build the plan ran onto a second A4 page, with small text and small buttons on a phone. Claude only knew from reading the code. After prompt 3 it printed on one page.
- **Choosing what a task waits for does not move it.** In the form, picking the task it can't start until doesn't change the start date. If you save a start that is too early it warns you and marks it in red on the chart; fixing the date is up to you.
- **No lines between rows.** The dashed line for a task that has to wait sits in its own row, running from the day the other task finishes. Claude said it left out lines between rows because it could not test them.
- **Small things on a phone.** The buttons are a little under our 44-pixel size, and the chart is 4 pixels wider than its box. None of it stopped the chart working.
- **The plan is not shared.** Each person's plan stays in their own browser, and the example plan greets everyone who opens the link. To share a plan you send the saved file; a live shared plan would need a database. Claude offered to start with a blank plan instead.

Live demo (Claude's unedited files, a made-up example): https://demo.iwantaito.com/make-me-a-gantt-chart/

## From the same studio

Ours: made by the same studio that runs this site.

- [How to get AI to](https://howtogetaito.com/): Its 'organise my schedule' guide gets AI to turn a list of jobs and dates into a plan you can paste in here.
- [Adapt Progress Evolve](https://adaptprogressevolve.com/): We build these properly, if you'd rather not do it yourself.

## Related

- [I want AI to build me a dashboard, CRM or spreadsheet tool](https://iwantaito.com/asks/build-me-a-dashboard/)
- [I want AI to build me a budget tracker](https://iwantaito.com/asks/build-me-a-budget-tracker/)
- [I want AI to build me a website](https://iwantaito.com/asks/build-me-a-website/)

## Sources

- [Claude help: create and edit files with Claude (all plans; Settings > Capabilities)](https://support.claude.com/en/articles/12111783)
- [GitHub Docs: adding a file to a repository (Add file > Upload files; 100 files at once, 25 MiB each)](https://docs.github.com/en/repositories/working-with-files/managing-files/adding-a-file-to-a-repository)
- [Cloudflare Pages: Git integration (Connect to Git; deploys on every push)](https://developers.cloudflare.com/pages/get-started/git-integration/)
- [Cloudflare Workers pricing ('Requests to static assets are free and unlimited')](https://developers.cloudflare.com/workers/platform/pricing/)

## Questions people ask

### Can AI make me a Gantt chart?

Yes, in our run. Five prompts gave us one file: tasks drawn as bars on a calendar, coloured by person, with tick-boxes, sections, tasks that wait for others, and Save to file. Every bar started and ended on the right dates in our tests.

### Can I make a Gantt chart for free?

Yes. Claude's Free plan made the file, GitHub's Free plan holds it, and Cloudflare says requests to static assets are free and unlimited. There's no account and no subscription.

### Can everyone on my committee see and edit the same chart?

Not with this version. Each person's plan is stored in their own browser, so changes on one phone don't reach another. You share by sending the saved file, and they load it. A shared live chart would need a database behind the page.

### Does it work on a phone?

Yes, with some rough edges. The whole ten weeks fit across a 390-pixel screen in our tests, with each task's name above its bar. A few buttons are a little small to tap, and we did not test a real phone or loading a file on one.

### Can I print it?

In our test, the example plan came to one A4 landscape page with the buttons hidden. The first build ran to two pages. A very long plan may need to run over, so try a print preview with your own tasks.

### Do I need to use a terminal or install anything?

No. You type in a Claude chat, download the file it makes, and upload it to your repository on the GitHub website. Cloudflare publishes it from there.