Create a proposal — from one requirement to strategic design

Write “store owners register menu items; customers pick items, order, and can cancel before the store accepts” in plain language to create your first proposal, then read the strategic design Claude Code splits it into (processes · bounded contexts · features · user stories · acceptance criteria) and the Impact Map.

Why a proposal#

In Robo Architect you don't change code directly. When you want to change something, you first create a proposal. One proposal is one change, and it keeps the whole history, from “what are we changing and why” (strategic design) to “how did we build it, and did we build it right” (implementation and validation). So when someone later asks “why does this aggregate exist?”, you open that proposal.

The first stage of a proposal is INTENT. It splits the requirement sentence into the vocabulary of domain-driven design (DDD).

Hands-on 1 — Create a proposal#

1. On Home, click the Proposals card to open the Proposals tab.
2. Click + New Proposal at the top right.
3. Type the requirement into the input box.

   Hanbit Delivery: Store owners can register menu items, change their prices, and mark them as sold out. Customers can pick menu items and place an order, and can cancel the order until the store accepts it.
   

4. Leave the mode at Simplified (Intent → Plan). Detailed DDD confirms the DDD stages Discover → Decompose → … → Tactical one by one, and ODA Standard designs on the basis of the TM Forum ODA standards.
5. Click Start AI Analysis.

The analysis is done by Claude Code on your computer, following the robo-proposal-intent skill. The progress window streams the tools Claude uses and its reasoning as they happen. It's normal for every legacy graph search (cluster_retrieve) to end with “0 legacy candidates · 0 rules found” — no existing code has been analyzed yet (once you analyze existing code in Chapter 13, evidence shows up here). One of the searches may be a Korean rewording of the requirement: the skill instructions are written in Korean, so Claude also tries Korean keywords in case the existing code uses them.

In this tutorial, “Proposal PRO-001 draft has been created.” appeared after about 2 minutes (127 seconds), without any clarification questions. Click View Proposal.

Hands-on 2 — Read the strategic design#

The first section of the proposal detail, Intent (Strategy), is the strategic design. The title is taken from a representative user story (“Store owner: register a menu item”), and the status is INTENT.

This is what came out in this tutorial. Your names and counts may differ a little.

The description of “Ordering” shows why it is Core — it owns the order lifecycle (awaiting acceptance → accepted / cancelled), this service's core rule. Scroll down and each user story has its acceptance criteria.

For example, “Customer: cancel an order before the store accepts it” came with these criteria.

Given my order in the 'Awaiting acceptance' status, When I cancel it, Then the order becomes 'Cancelled' and the store can no longer accept it
Given my order already accepted by the store, When I try to cancel it, Then the cancellation is rejected and the order stays 'Accepted'
Given an order that belongs to another customer, When I try to cancel it, Then the request is rejected
Given a cancellation and a store acceptance for the same order arrive at nearly the same time, When both are processed, Then only the first one takes effect and the other is rejected

The criteria cover edge cases that weren't in the requirement sentence (an order already accepted, someone else's order, a cancel and an accept arriving at the same time). In Chapter 7 these criteria become the tests that validate the implementation.

The buttons at the bottom let you correct the result.

Hands-on 3 — The Impact Map#

The Impact Map section shows what this proposal creates and what it changes in the existing design, by Requirements · Process · Design. The project is empty for now, so everything is New. When you create a second proposal in a project that already has a design, “Modified” items show up too (Chapter 9).

What to check#

• PRO-001 is in the proposal list with status INTENT.
• The strategic design has processes, bounded contexts (at least one Core), features, user stories and acceptance criteria.

Quiz#

1. Why do you think the “Ordering” context was classified as Core and “Menu Management” as Supporting?
2. The legacy graph search during analysis ended with “0 legacy candidates”. Is something wrong?
3. If the result isn't what you expected, how do you fix it? Name two ways.