Plan the project before you build

What it's for

In code projects, Plan mode is a conversation about what the site should be, before and during the build. The architect writes a document, the project plan, which sits in the Plan tab next to the chat. Use it when the project is large, when you don't know every page yet, or when you want to settle the details before spending credits on code.

What the plan covers

• The business: who the company is, what it sells, to whom and where.
• The site's goal: what a visitor should do, such as buy, book, ask for a quote or sign in.
• The pages: each with its address and what it shows, section by section.
• The menu and footer, and the look: colors, fonts, tone and images.
• Data and access, when the site stores data or has sign-in: the tables, the fields and who may see or change what.
• The rules: what must always or never happen, such as no invented numbers, prices only if you give them, the language and legal texts.

How to use it

1. 1

   In the project chat, choose Plan

   The switch sits next to the send button. The Plan tab opens alongside.

2. 2

   Describe what you want to build

   You can also attach a text file with your specification. Images aren't accepted in this mode.

3. 3

   Read the plan and ask for changes

   Each completed request creates a new version of the plan, and the chat shows Plan updated · version N.

4. 4

   Choose how to build

   Generate tasks breaks the plan into tasks on a board, to build one by one. Build the whole plan builds it all at once and returns a proposal to review, with Apply, Preview and Discard.

If you only ask a question, the architect answers in the chat without creating a new version of the plan.

The plan and Build mode

Once a plan exists, every request made in Build mode is sent along with it, so the AI keeps to what was agreed. If the plan changes, the next requests follow the new version.

The mode you pick is remembered for each project, in this browser.

Plan versions

Under Versions in the Plan tab you'll find every version of the plan. Restore brings an earlier one back as the current version, free and without touching the code.

Build through the tasks

Once the plan is right, click Generate tasks in the Plan tab or type “approved” in the Plan mode chat. The architect breaks the plan into tasks on a board, the way agile teams work, written in plain words. Each task says who wants what and why (“As a visitor, I want…, so that…”), the Expected result and Where on the page the change goes.

1. 1

   Open Tasks in the Plan tab

   The board has four columns: To do, In progress, Testing and Done.

2. 2

   Click Send to chat on the task you want built

   It goes into the chat box, in Build mode, with a request ready. To send several together, tick them and use the button at the top of the board.

3. 3

   Send the request

   The tasks move to In progress. Once the change is applied, they go through an automatic check of the code.

4. 4

   Follow the result

   What the check finds in the code moves to Done, with what it saw. What is missing goes back to To do with the reason, so you can ask again.

Above the plan document, a bar shows how many tasks are done and lists what is left. You can also move a task by hand, with its arrows or by dragging it to another column, and use Test now on a task in progress. If the plan changes later, Update tasks adds the tasks the current version is missing, without deleting or changing the ones on the board. If there is nothing new, the credit comes back.

To add a task of your own, click New task at the top of the To do column and write what needs to be done; how to tell it is done and where on the site are optional. Or ask in the Plan mode chat, for example “create a task to standardize the buttons”: the architect creates only that task, without changing the plan. Tasks you create are marked Yours. Only you can delete a task in To do, with the bin icon on the board itself: the chat and the AI never delete tasks.

If you undo a change, with Undo this change in the chat, from History or by asking to go back to a version, the tasks done in it go back to To do with a red tag saying which version held the change. Send them to the chat again when you want it redone.

What it costs

If the architect fails to update the plan, the credit goes back. A plan for a whole site may be built in steps, with the steps and credits shown first; and if your credits aren't enough, the chat suggests building one part at a time.

Frequently asked questions