Car Fleet¶
The constitution is done. The coding guidelines are connected. The roadmap starts here.
Feature 1 is the simplest: give staff a place to register cars. Every other feature — bookings, pricing, billing, wizards — depends on a car existing as an Item record. So this is where we begin.
What you'll build¶
A car in this system is a standard Non-Inventory Item with Base Unit of Measure = DAY. Nothing custom about the document type — just an Item, used exactly as BC intended, with a small extension to hold the vehicle fields the brief needs: plate, VIN, make, model, year, mileage, fuel type, transmission, next inspection date.
At the end of this feature, staff can:
- Open the Item Card for any car
- See and fill in all vehicle fields in a dedicated Vehicle group
- Attach documents and photos via the standard Document Attachments FactBox
- Save the record without errors
That's the whole feature. Simple, grounded in standard BC, nothing invented.
Switch to workspace view¶
If you closed the workspace earlier to run the coding guidelines skill, switch back now:
File → Open Workspace from File… → select workshop.code-workspace
The workspace gives the agent visibility into all project folders simultaneously — app/, specs/, external/MSDyn365BC, .cursor/rules/ — which it needs for the implementation steps ahead.
One chat, one feature rule¶
Open a fresh chat now and stay in it through every step: spec, implement, test, docs, and merge. The spec files and the constitution are all the context you need — no conversation history required.