Plans
Your agent writes the plan with you. Then your coding agent builds it step by step, and asks you here when it needs a call.
Free for 3 days, then $12 a month.
1 of 4 steps done · Being worked on: Booking page
Should groups pay up front or at the door?
Codex is waiting for this, and carries on the moment you answer.
Nothing needs you right now
Planned 4 steps: Data model, Booking page, Payments for groups and Reminders for each seat.
Seats are in: each class now knows how many it has.
1Data modeldone2 tasks doneThe class page shows the seats left. Booking several at once is next.
2Booking pagebuildingShould groups pay up front or at the door?
Codex is waiting for it3Payments for groupsYou chose: Up front
Codex has it
Booking several seats at once works, so the booking page is done. Starting on payments: groups pay up front.
2Booking pagedone1 task doneOn the whole plan Your agent reads it at its next update.
A class books as one link with seats, up to 20.
Studios that run group classes, and the members who book them.
A studio shares one link for a class, members book a seat each, and each gets their own reminders.
Seats on a class, each with its own booking.
A seats table keyed to the class, so a class of 20 holds 20 bookings.
db/schema.sqlsrc/classes/seats.ts
One page for a class, with the seats left.
The class page reads the seat count live, and a member can take more than one seat in one go.
src/booking/ClassPage.tsxsrc/booking/SeatPicker.tsx
Should groups pay up front or at the door?
Up frontChangeUp front or at the door.
One checkout for every seat in a booking, and a refund to each member when a class is cancelled.
src/pay/checkout.tssrc/pay/refunds.ts
Every seat gets its own reminders.
Each member who books a seat gets the class reminder, in their own language.
src/reminders/send.ts
3 pictures from your coding agent, newest first.
Paste this into Codex or Claude, in your project. It builds the plan, and tells you how it is going in this plan’s thread.
1 of 4 steps done, so it finishes step 2, “Booking page”, first.
2 of 4 steps done, so it finishes step 3, “Payments for groups”, first.
Carry on building the plan on my Context Board plan board “Group bookings”, here in this project. Some of it is built already, so start from where it stands. Where it stands: - Step 1 is built. Don’t build it again, but read it first for context. - Step 2, “Booking page”, was being built: a session before you started it. Read its tasks and history to see how far it got, and finish it first. - After that, steps 3 and 4 are still to build. - 1 question on the plan still waits on me.
Carry on building the plan on my Context Board plan board “Group bookings”, here in this project. Some of it is built already, so start from where it stands. Where it stands: - Steps 1 and 2 are built. Don’t build them again, but read them first for context. - Step 3, “Payments for groups”, was being built: a session before you started it. Read its tasks and history to see how far it got, and finish it first. - After that, step 4 is still to build.
1 of 4 steps done · Being worked on: Booking page
Should groups pay up front or at the door?
Codex is waiting for this, and carries on the moment you answer.
Nothing needs you right now
Planned 4 steps: Data model, Booking page, Payments for groups and Reminders for each seat.
Seats are in: each class now knows how many it has.
1Data modeldone2 tasks doneThe class page shows the seats left. Booking several at once is next.
2Booking pagebuildingShould groups pay up front or at the door?
Codex is waiting for it3Payments for groupsYou chose: Up front
Codex has it
Booking several seats at once works, so the booking page is done. Starting on payments: groups pay up front.
2Booking pagedone1 task doneOn the whole plan Your agent reads it at its next update.
A class books as one link with seats, up to 20.
Studios that run group classes, and the members who book them.
A studio shares one link for a class, members book a seat each, and each gets their own reminders.
Seats on a class, each with its own booking.
A seats table keyed to the class, so a class of 20 holds 20 bookings.
db/schema.sqlsrc/classes/seats.ts
One page for a class, with the seats left.
The class page reads the seat count live, and a member can take more than one seat in one go.
src/booking/ClassPage.tsxsrc/booking/SeatPicker.tsx
Should groups pay up front or at the door?
Up frontChangeUp front or at the door.
One checkout for every seat in a booking, and a refund to each member when a class is cancelled.
src/pay/checkout.tssrc/pay/refunds.ts
Every seat gets its own reminders.
Each member who books a seat gets the class reminder, in their own language.
src/reminders/send.ts
What it does
Planned, building, done, blocked, waiting, later or dropped. Your coding agent marks each step as it goes, with what proves a done step works, and ticks its tasks.
When a step needs a call only you can make, your agent puts the question on the plan with its options and the one it would pick. Click an answer, or type your own, and the agent that asked gets it the moment you answer.
Hand off gives you the words to paste into Claude or Codex in your project. Hand it on again later and it starts from where the build stands.
Your coding agent sends its mockups, and a screenshot whenever a step changes how something looks. They gather in Previews, before and after side by side.
The goal, who it is for, what done looks like, and a diagram of how the steps fit. Each step in the diagram takes its status colour as the build moves.
Write a note on the whole plan or one step. Your agent reads it at its next update, and the thread shows when it has it.
Ask your agents
You ask: Break group bookings into steps
An Overview and four steps, each with its tasks
You ask: Build the next step on the Group bookings plan
Booking page marked built, with a screenshot in Previews
You ask: Add a step for a waitlist when a class is full
A fifth step, Waitlist, with its tasks
Also try Claude: “What’s waiting on me?”
Works with
Who it’s for
Plan it with your agent, then answer the few calls only you can make.
Write what done looks like, and every builder, person or agent, works from it.
Questions from every agent on the job wait in one plan for you.
One workspace
Read more
Price
Something else on your mind? Get in touch.
Setup, connections and every limit are in the docs.
No. The board’s own chat plans with you and never builds. When the plan is ready, Hand off gives you the words to paste into Claude or Codex in your project, and that agent builds it step by step.
It puts the question on the plan, with its options and the one it would pick. You answer with a click or in your own words under Needs you, and the agent that asked gets the answer the moment it lands.
No. Each step keeps its status, its tasks and the agent’s latest message, so you can come back later and see what was built, what is being built and what waits on you.
Yes. Add a step on the left, edit any step’s page, or leave your agent a note in the thread. It reads your note at its next update.
Any app that connects to Context Board over MCP can read and update a plan, including Claude, ChatGPT, Codex, Cursor and VS Code. Building works best with a coding agent that runs in your project.
Context Board is free for 3 days, then $12 a month for the whole workspace: plans, docs, sheets, dashboards and every other kind of board. The board’s chat runs on the Claude or Codex plan you already pay for, so there are no AI credits to buy.
Plans sit beside docs, files, mind maps and every other kind of board, in one workspace your agents work in with you.
Free for 3 days, then $12 a month.
