Planning and teamwork
One giant sticky note
Welcome to the studio. You're the newest teammate, and on the wall there's one big sticky note: ship Hyper Shards.
Kai and Remy's old way was "open the chat and see what happens". But a goal that big can't be started on a Monday afternoon. Where would you even begin?
Real studios turn a big goal into a plan made of small pieces.
Goal, milestones, tasks
- GoalThe big finish line: ship Hyper Shards as an app people can install from our website.
- MilestonesCheckpoints on the way, each one a version you can play. For example "controls feel great", then "five waves of aliens".
- TasksThe small jobs inside a milestone, like "stop the ship sliding after key release".
Bolt says: A milestone is something you can show. A task is something you can finish.
Quick check
Which of these is a milestone for Hyper Shards, not a task?
- Five waves of aliens, all playable
- Change laser damage from 2 to 3
- Fix a typo on the title screen
Show the answer
Five waves of aliens, all playable
A milestone is a playable checkpoint that holds many tasks. Changing one number or fixing one typo is a single small task.
The task board
- To doEvery task we plan to do, with the most important at the top.
- DoingTasks someone is working on right now. Each card has one owner.
- DoneFinished and tested. Moving a card here feels great.
A task board shows every task as a card in one of three columns. Cards move from left to right.
Bolt says: Keep Doing short: one card per person. Ten half-finished tasks are worth less than one finished task.
Our board lives on GitHub
Our code will live on GitHub, a website that stores code and its whole history, so our board can too. A GitHub issue is one task card: a title, a description and a number, like #12.
A GitHub Project shows those issues as a board with columns, so the whole team sees who is doing what.
Later in this stage you'll see how a code change can link to an issue, so the card closes itself when the fix is finished.
Quick check
On our board, each person should keep as few cards in Doing as possible, ideally just one.
- True
- False
Show the answer
True
Finishing beats starting. With one card each in Doing, work actually gets done, and everyone can see who is working on what.
Small, clear tasks
A good task is small enough to finish in one work session, and it says what "done" means.
Too big: "Make the shop."
Just right: "Shop button opens the shop screen. Done when tapping it in Garden Defense shows the seed list."
The same rule works for AI agents, AI helpers that can do a job with several steps on their own. Give each agent one clear task, not a whole milestone, so you can check its work in a few minutes.
Task pick
Remy wants to hand one card from To do to an AI agent. Which card is small and clear enough?
- "Make Garden Defense fun"
- "Add a snail pest: slow, 3 health, worth 5 coins. Done when one crawls to Sprig in level 1."
- "Finish all the levels, the shop and the sound"
Show the answer
"Add a snail pest: slow, 3 health, worth 5 coins. Done when one crawls to Sprig in level 1."
It is one job with exact numbers and a clear "done" test. "Fun" can't be checked, and the last card is a whole milestone squeezed onto one card.
Who does what
- RolesKai leads gameplay code. Remy leads art, sound and the shop. A role says who decides, not who is allowed to help.
- Your partYou take cards like everyone else. You also play-test each new version and report what feels wrong.
- Weekly goalEach week the team picks one goal, like "the shop works". Cards that don't help it can wait.
- Quick check-insA few minutes, a few times a week. Everyone says what they finished, what is next, and what has them stuck.
Our first week
This week's goal: build a real workshop. The cards are already on the board: set up Antigravity 2.0, learn the command line, meet Claude Opus 5.5, write better prompts and split the code into modules.
Then come the Git cards: commits, push and pull, branches, merge conflicts, pull requests, then automated tests and the robot tester that runs them.
Each card is one lesson in this stage. Time to pull the first one into Doing.
Bolt says: First card: our workshop. Next lesson, meet Antigravity 2.0.
Fact-checked 9 October 2026
- GitHub Docs: About issues docs.github.com
- GitHub Docs: About Projects docs.github.com
- GitHub Docs: Linking a pull request to an issue docs.github.com