Planning and prompting

Plan mode inspects the project and proposes a strategy without changing your app's source files. Use it for a new workflow, a larger redesign, or a change that affects stored data. Build mode implements the requested work, prepares a preview, and attempts to repair detected failures.

Planning is a decision point, not a guarantee that every requirement has been understood. Read the plan before approval and correct anything that would make the finished app wrong.

• Audience: who uses the app, and what do they need to accomplish?
• Workflow: list the steps from arrival to a successful result.
• Data: name the fields that should be saved and who may access them.
• Rules: specify constraints, calculations, and validation requirements.
• Presentation: describe the visual direction and provide any real content.
• Acceptance criteria: explain what you will test to decide the work is complete.

Add cancellation to the booking workflow.
Keep the existing service choices and page design.
Let a customer cancel only their own booking.
Ask me about the cancellation deadline before choosing one.
Verify that another customer's booking cannot be canceled.

State the current behavior, the desired behavior, and what must stay unchanged. For a bug, include the page, input, and visible result. Work in small reviewable changes so you can identify which update caused a problem.

• Prefer: ‘The confirmation disappears after reload; save the booking and show it again.’
• Avoid: ‘Make everything better.’
• For a redesign, name the elements that should change rather than asking for an unrelated rebuild.