MyJackfruit

Help
Browse topics · Starting

Starting

← Starting

When do I actually start making the app?

Short answer

Right after you approve the plan: Kai-Zen then starts the first step, a small piece of the app, and has it built.

Before you start

Words used here (1)
Kai-Zen
Kai-Zen is the planning agent: it finds out what you want, chooses the way, hands the work to other agents and reports back.
Deeper

Also asked:

When do I actually start creating the app? Right after you approve the plan: Kai-Zen then starts the first step, a small piece of the app, and has it built. Only a ready-made sign-in may be set up earlier, while the plan is written.

Building starts when planning ends. For a new project, Kai-Zen, the planning agent, asks what only you know in one round of questions, writes the whole plan from the top down, makes it more exact, and suggests the steps to deliver it. It stores all of it in the project's vault, reads it back, and shows you the whole plan for one approval before the first coding brief, the first instructions for writing code, unless you said in your own words that you need none. After your approval it starts the first round of delivery with the first suggested step.

One thing can start earlier. For a GilbPlatform app, an app built on GilbPlatform, the builder may install the ready-made sign-in from GilbPlatform's code bank, a store of code to reuse, while the plan is written. It builds no screens then. If you said no code before the plan is stored, it waits for the first coding brief.

What is a step? A step is a small piece of your app that is built, put live and measured in one short round. Each step is as small as possible while it still brings something that can be measured, such as how many customers can now book a time. A step counts as delivered only when the people it is for can use it, not when it works on a test copy. The first step sets up the base of the app, a ready-made core app with a sign-in, plus something useful for you if it can. In GilbApp's Plan, a step is made with New value delivery step; the answer How do I write a step? shows its card.

Each round runs the same way. Kai-Zen picks the step and hands it to the builder: for an app on GilbPlatform, Agent.Coder, the agent that builds apps; for any other kind, the place the project names. The step is checked by Agent.Scaling, the agent that checks what was built, and tested by Agent.Tester, the agent that tests what others built, a separate agent from the builder. If Agent.Coder cannot start a separate tester, it tests the step itself and says so. Then Kai-Zen asks for your go before it puts the step live, asks you to check it live, and has what it brings measured. Then it shows you the results and the next step, and goes on until you say re-plan or done. The answer How does Kai-Zen run a whole delivery cycle? tells more, and the answer How do I pick the next step? shows how to ask for a step yourself.

Is my plan good enough to start? You do not have to judge that alone. Before it shows you the plan, Kai-Zen makes it more exact: it checks, part by part, that the plan has what it needs to judge each part above and to deliver each part below, challenges each Solution twice against another way of doing it, and checks that each Value has where it stands now, the lowest level you can accept, and its goal. A Function is something your app must do, a Value is a goal for how well it must do it, and a Solution is a way to build it. At the approval it lists what is still weak: every assumption, a choice Kai-Zen made for you that you can change; every Value you set that is hard to reach; every Value that supports nothing above it; and every open point.

The plan does not have to be perfect. The order of the steps is a forecast: before each step Kai-Zen picks it for real and changes the forecast with what it learned, and after each step it makes the plan more exact again. So at the approval, ask yourself whether the plan says what you want: who the app is for, what it must do, and what should come first. If it does not, reply with what you want changed; Kai-Zen changes it and asks once more.

Building needs Claude Code in Terminal, the window where you type commands (on a Mac, the Terminal app), on your computer: Agent.Coder works on code kept there, and GilbApp's chat does not reach the files on your computer unless you choose a code folder while Claude Code is connected. The answer How do I let my AI build in a folder on my computer from GilbApp's chat? shows how. The answer What do I need to get started? lists what Claude Code needs.

This answer is written for a computer screen.

Source: Standards: Kai-Zen.New (Setup, Standard, Down, Sharpen, Steps, Show, Cycle); Kai-Zen.Sharpen (Up, Down, Challenge, Repeat); Kai-Zen.ValueDeliveryStepRules (First, Small, Forecast, Learning, Delivered); Kai-Zen.Cycle; Kai-Zen.AskRules (One, EndApproval); Agent.Coder (Role, ProjectFolders). GilbApp 96968de7, src/shell/gilbAppMenuRows.ts:162 (Plan), src/components/records/TableCard.tsx:617 (New value delivery step). Live answers: How do I start my first plan?, How do I set up a project's kind and standards?, How big should my first version be?, How does Kai-Zen run a whole delivery cycle?, How do I pick the next step?, How do I write a step?, Can I start with only GilbApp, without setting up my computer?. Code-folder exception: GilbApp 49b1ae53 (https://gilb.com/app/version.json, read 13 November 2026), src/components/agent/AgentChat.tsx:677-692 and :1084-1090 (Choose a code folder, Code in, Claude Code only); live answer How do I let my AI build in a folder on my computer from GilbApp's chat?

Checked against GilbApp d529620.