Handle a change during the build

Decide where a change belongs: the model, the design system, or the code.

Fetch https://ntent.app/r/task/model-or-code.json and follow it. Stop and ask me at any step that says to, and do not decide something on my behalf that the plan says is mine to decide.

The steps

Here so you can follow along, or do it yourself. Your agent gets the same list from the plan above.

1. 01

   Name the kind of change

   There are 4 kinds, and each goes somewhere different. Scope: the product starts or stops doing something. Behaviour: a rule, a field, a stage, a journey step, a calculation, or wording that changes what a user is promised. Shared system: a colour, a component, or a pattern every screen uses. Presentation: spacing, animation, column order, or where a button sits on one screen. Decide which kind this is.

   Success check: You can name the kind without discussing it. If two people name different kinds, that is the conversation to have first.

2. 02

   Scope and behaviour go to the model

   Change the model first, then the code. A scope change needs the product owner to agree, because it changes what was agreed. A behaviour change needs whoever approved that rule. An error message counts as behaviour if it changes what the user is told will happen. Otherwise it is presentation.

   Success check: The model changed before the screen did, and the rule’s provenance says who agreed.

3. 03

   A shared-system change goes to the design system

   It changes how everything looks, not what the product does, so it does not go in the model. Change the colour, spacing value, or component in the design system itself. Run the probes and the token check, then tell everyone else building screens.

   Success check: One change, every screen moved, no screen edited by hand.

4. 04

   Presentation stays in the code

   Just change the screen. Nobody else is affected.

5. 05

   Resolve open questions

   If you are not sure, ask the product owner. If their answer changes how the product behaves, write it in the model.