Algoritmi AI SandboxPractice environment with sample data. Nothing here reaches the production platform.

Bigger Features

For a feature that spans several screens, make a plan first and work through it in small stages.

When to use this

  • You want a feature that spans several screens
  • How the data is stored needs to be thought through
  • One request will not be enough

For a change that takes one request, use Small Changes.

The idea

When a large feature is built all at once, there is too much to check and mistakes are easy to miss. So work like this:

  1. Make a plan for the whole feature first
  2. Split the plan into small stages
  3. For each stage, check the screen, create a PR, and merge

The production app gets a little better with every stage, and you can change direction along the way.

Step 1: Ask for a plan

In Claude Code, select the algoritmi-sandbox-vibe-coding-platform folder, start a new conversation, replace the parts in 【 】 below, and send the request.

Ask for a plan in stages
Claude prompt
I want to add the following feature to 【app name】. What I want: 【Example: filter lost items by "In storage", "Returned", and "Disposed". Also add a screen that shows the number of items per month】 I think this is too large for one request, so please work as follows. I have no programming experience. 1. First read this app's CLAUDE.md and PLAN.md 2. Make a plan that splits the work into a few small stages and explain it without technical terms. For each stage, say what a person will be able to do on screen once it is finished 3. Mark any stage that needs a change to the database structure or to anything under shared/ 4. Do not change any files until I say OK
Use plan mode

Claude Code has a plan mode, in which Claude only makes a plan and does not change files. In the desktop app, choose Plan from the permission mode selector. When you are happy with the plan, leave plan mode and have Claude continue.

Step 2: Check the plan

Check these points:

  • Is it clear what you will be able to do when each stage is finished?
  • Is the first stage small enough to start with?
  • Does it include anything you did not ask for?

If a stage is marked as changing the database, share the plan with an administrator too.

Step 3: Save the plan and do the first stage

When you are happy with the plan, send this request.

Save the plan and ask for the first stage
Claude prompt
This plan is OK. Please work in this order. 1. Create a new branch from main, save the plan under ai_docs/plans/ in 【app name】, and update PLAN.md 2. Then build only the first stage and confirm that the build passes 3. Commit, create a pull request to main, and give me the PR URL. I will move on to the next stage after I merge

When the stage is ready, check it on the screen Claude opens (Check the Screen). When the PR exists, follow Check and Merge to merge.

Step 4: Do the next stage

After merging a stage, ask for the next one in a new conversation. The plan is saved inside the app, so Claude reads it and carries on from where you left off.

Ask for the next stage
Claude prompt
Read PLAN.md and the plan under ai_docs/plans/ in 【app name】. The previous stage has been merged. Bring main up to date, create a new branch, and do only the next stage. Before you start, explain what this stage does without technical terms, and wait until I say OK. When you are done, confirm that the build passes, update PLAN.md, create a pull request to main, and give me the PR URL.

Repeat this until the last stage.

Merge the previous stage before starting the next

Do not ask for the next stage before the previous PR is merged. Changes pile up on each other, and you may end up unable to check or merge them.

If you want to change the plan partway

Changing your mind after trying something is normal. Revise the plan, then continue.

Ask to revise the plan
Claude prompt
I want to revise the plan for 【app name】. What I want to change: 【Example: before the monthly totals, I want to be able to print the list】 Explain how you would rewrite the plan under ai_docs/plans/ and PLAN.md to match. Rewrite them only after I say OK.

If you want to rebuild an app

If you want to change how an app is built from the ground up, talk to an administrator first. The effect on the people using it and on the stored data is large. Claude can examine the current app to give you something to discuss.

Discuss how a rebuild would go
Claude prompt
I am thinking about rebuilding 【app name】. Do not do any work yet. Current problem: 【Example: after adding feature upon feature, the screens have become confusing】 What I want: 【Example: reduce it to the three screens people use most】 What must be kept: 【Example: the data registered so far】 Examine how the app is built now, then explain, without technical terms, how a rebuild would proceed and what to watch out for.

Quiz

Quiz

Your plan has three stages and you have merged the PR for the first one. How do you start the next stage?