Implement in a sandbox

Split the confirmed plan into a task list, and the Claude Code cell in the Code tab implements that list item by item with /robo-implement. The work happens not on the main branch but in a worktree (the sandbox) on the proposal/PRO-001 branch, with a commit for each finished task. In this tutorial, 18 tasks took about 35 minutes.

What happens#

• Task list — the robo-proposal-tasks skill turns the plan (Chapter 5) into a checklist by phase. Each task lists the file paths it will create.
• Sandbox — a git worktree is created at .sandbox/proposal/PRO-001 inside the target project folder, and the work happens on the proposal/PRO-001 branch. The main code stays as it is until acceptance (Chapter 7).
• Claude Code cell — in the terminal on the right of the Code tab, Claude Code on your PC runs /robo-implement PRO-001. Each time it finishes a task, it ticks the checkbox in PROPOSAL_PRO-001_TASKS.md and commits.
• Progress — the proposal's Sandbox Implementation section reads those checkboxes and shows a progress bar and per-phase counts.

Hands-on 1 — Generate the task list#

1. In PRO-001, whose plan you confirmed, open the Sandbox Implementation section. Check that the target project is the code folder you chose on Home (…/projects/hanbit-delivery-en).
2. Click Generate task list. Claude Code reads the plan and writes tasks by phase. In this tutorial it took about 4 minutes. If it stops with “Failed to parse the task breakdown”, Claude's answer couldn't be read as a task list — click it again (this time it worked on the first try).
3. Implementation Task List · 18 tasks appears. Each task has a description and the files it will create. If you don't like it, click Regenerate task list.

This task list had eight phases.

You can see the decisions of the Chapter 5 plan turned directly into tasks — for example, T011 says each handler “calls MenuCatalogQuery through the menu-management public index” for the item's store, current price and availability, and T010 adds “no foreign keys to menu_ tables” (constitution principle I, Bounded Contexts as Modules). T017 then adds an architecture test that Ordering SQL never references menu_ tables.

Hands-on 2 — Start implementing#

1. Click Start implementation. The app creates the worktree and the proposal/PRO-001 branch. If the target folder isn't a Git repository, it asks whether to run git init and continue.
2. Click Go to Claude Code cell. The Code tab opens with a PRO-001 cell on the right.
3. The first time, Claude Code asks two things. Click the cell, choose with the arrow keys and press Enter.
   ① Folder trust — “Yes, I trust this folder” (the default is “No, exit”, so be sure to move down to it)
   ② Bypass permissions mode consent — “Yes, I accept” (so that file writes and commands during implementation aren't confirmed one by one)
4. Once you've answered both, the app types /robo-implement PRO-001 into the cell and implementation starts. While a prompt is on screen, the app doesn't send the command and waits.

Hands-on 3 — Watch the progress#

In the cell you can watch Claude Code read and write files, run npm install and tests, and git commit. Go back to the Proposals tab to see the progress bar.

• Progress bar · per-phase counts — updated each time the cell ticks a checkbox in PROPOSAL_PRO-001_TASKS.md. Finished tasks are struck through, and phases that are done fold up to their count.
• “Stalled — no update for Nm” — appears when the checkboxes haven't changed for a while. Open the cell and see what Claude is waiting for (a question, an error).
• Stop · further instructions — stop with Ctrl+C or Esc in the cell, then type further instructions.
• Mark remaining done — if the run ended with some tasks left over, this moves on to validation with what has been done so far. To have Claude finish the rest instead, give it further instructions in the cell.

In this tutorial, all 18 tasks were done about 35 minutes after answering the prompts.

Result — what was created#

The proposal/PRO-001 branch got one commit per task, 18 in all (T001: scaffold npm-workspaces monorepo … … T018: one deployable unit …). Excluding the lock file, that's 125 files and 9,290 lines.

backend/src/modules/menu-management/   MenuItem aggregate · commands · StoreMenu query · MenuCatalogQuery port · routes
backend/src/modules/ordering/          OrderDraft · Order aggregates · commands · queries · routes
backend/src/shared/                    SQLite · transactions · events · HTTP errors · dev actor stub
backend/migrations/                    0001 menu_items · 0002 ordering tables
backend/tests/                         process-level API tests · module-boundary tests · acceptance traceability
frontend/src/features/menu/            store menu · owner menu management · register form · change price dialog
frontend/src/features/ordering/        order review · order status · incoming orders
Dockerfile                             one deployable unit (Node.js LTS slim, SQLite file on a volume)

This code exists only in the sandbox for now. It is merged into the main branch only after it is validated and accepted (Chapter 7).

What to check#

• The task list is shown by phase, with file paths on each task.
• In the cell, you answered “Yes” to folder trust and bypass permissions the first time, and /robo-implement PRO-001 then started by itself.
• The progress bar reached 18/18, and the proposal/PRO-001 branch has a commit per task.

Quiz#

1. Does the main code (the default branch of hanbit-delivery-en) change during implementation?
2. The cell is stuck at “Is this a project you created or one you trust?”. What do you do?
3. The progress bar shows “Stalled”. What do you look at first?