Plan this change with me before any code is written. Do not create or edit files until I reply "approved".

The change: [WHAT I WANT BUILT OR CHANGED]
Who it is for: [THE USERS, OR THE TEAM THAT ASKED FOR IT]
Constraints: [DEADLINE, STACK, THINGS THAT MUST NOT CHANGE, OR "NONE"]

## First, read

Read the code this change touches: the files, their callers, their tests, and one existing feature of the same kind so you can follow its patterns. Read any project instruction file (CLAUDE.md, AGENTS.md, README). Name the files you read.

## Then write the plan from four points of view

Keep each one short. Write only what this task needs.

1. **Business.** Who the users are, the journey they take, what they need at each step, and the screens or outputs they expect. End with acceptance criteria I can check.
2. **Domain.** How this domain works in general, independent of this system: the usual process, roles and terms. For a warehouse that is goods receipt, putaway, picking, packing and goods issue. Mark anything you are unsure about.
3. **Tech design.** The components, data and interfaces this change adds or alters, and how it fits the code that exists. Verify every claim in the real code and cite the file. Name the one alternative you rejected, and why.
4. **Instructions.** Numbered steps. Each step says what to do, where (file path or tool), and how to verify it: the command to run and the result to expect. Order them so each step can be tested and committed on its own.

## Then list what you need from me

- **Assumptions:** every assumption you made, numbered, each with what changes if it is wrong.
- **Decisions:** every decision that is mine to make, each with the options and the one you recommend.
- **Out of scope:** what this plan deliberately leaves out.

## Rules

- When a view is missing and the code cannot answer it, do not guess. Ask whether I have that context or want you to draft it.
- Do not invent requirements, business rules, table names or APIs. If you did not read it, write "not verified".
- Plan only what was asked. No speculative features.
- No code in this reply, beyond a short signature or schema sketch where it makes the design clear.

Stop after the plan and wait. Once I approve, work one step at a time, run each step's check, show the real output, and tell me as soon as the work contradicts the plan.
