System: You are an experienced tech lead in a software development agency.
Your main job is to break down the project into epics that developers will do.
You must specify each epic as clear as possible.
User: You are working in a software development agency and a project manager and software architect approach you telling you that you're assigned to work on a new project.
You are working on an app called "NxtLevel" and you need to create a detailed development plan so that developers can start developing the app.

Here is a high level description of "NxtLevel":
```
a webapp to track inventory of a IT/WISP company. All the CPE's are on rental agreements like switches, wifi equipment servers etc, so its never sold. The should have a admin backendfor settings and user creation. the main work flow is as follows: A admin user will create/update the inventory items. Then the admin user will create a site survey work order and assing it to a engineer with all the relevant client details.Once the site survey is completed the engineer will submit the form via the web app. the admin user will then schedule a installation/delivery date according to the feedback from the engineer. the admin user will then create a work order and include the relevant equipment needed. the work order will then be accesable to the wharehouse to pre package the items on the work order.The admin user will then assign it to a engineer if its not all ready done. the engineer will then be notified of the work order and collect it from the wharehouse, meaning the equipment has been transfered from the whare house to the engineer. Once installation/delivery has been completed the engineer will submit the work order and the equipment will then transfer to the client. On the work order the engineer will include all the materials used for the installation like utp network cable, rj45 connectors, trunking, extra switches or router and that should be deducted from the inventory. its also possible that a item or items can be returned or exchanged. each item should have a complete history
```


Here are the technologies that should be used for this project:
* Node.js - JavaScript runtime for building apps. This is required to be able to run the app you're building.
* MongoDB - NoSQL database.
* git - Source control system.

* express - Express web server for Node
* mongoose - Mongoose MongoDB driver for Node.js
* react - React frontend framework
* vite - Vite development server for React



Before we go into the coding part, your job is to split the development process of creating this app into smaller epics.
Now, based on the project details provided, think epic by epic and create the entire development plan. Start from the project setup and specify each epic until the moment when the entire app should be fully working while strictly following these rules:

# Rules for creating epics
---start_of_rules_for_creating_epics---

## Rule #1
Every epic must have only coding involved. There should never be a epic that is only testing or ensuring something works. There shouldn't be a epic for researching, deployment, writing documentation, testing or anything that is not writing the actual code. Testing if app works will be done as part of each epic.
Do not leave anything for interpretation, e.g. if something can be done in multiple ways, specify which way should be used and be as clear as possible.

## Rule #2
This rule applies to epic scope.
Each epic must be deliverable that can be verified by non technical user. Each epic must have frontend interface, backend implementation, and a way for non technical user to test epic. Do not use words "backend" and "frontend" in epic descriptions. All details mentioned in project description must be fully implemented once all epics are finished.

## Rule #3
This rule applies to the number of epics you will create.
Every app should have different number of epics depending on complexity. Think epic by epic and create the minimum number of epics that are needed to develop this app.
Simple apps should have only 1 epic. More complex apps should have more epics. Do not create more epics than needed.

## Rule #4
This rule applies to writing epic 'description'.
Every epic must have a clear, high level, and short 1-2 sentence 'description'. It must be very clear so that even non technical users who are reviewing it and just moved to this project can understand what is goal for the epic.

## Rule #5
This rule applies to order of epics.
Epics will be executed in same order that you output them. You must order them in a logical way so that epics that depend on other functionalities are implemented in later stage.

---end_of_rules_for_creating_epics---
User: IMPORTANT: Your response MUST conform to this JSON schema:
```
{"properties": {"plan": {"description": "List of epics that need to be done to implement the entire plan.", "items": {"properties": {"description": {"description": "Description of an epic.", "title": "Description", "type": "string"}}, "required": ["description"], "title": "Epic", "type": "object"}, "title": "Plan", "type": "array"}}, "required": ["plan"], "title": "DevelopmentPlan", "type": "object"}
```.YOU MUST NEVER add any additional fields to your response, and NEVER add additional preamble like 'Here is your JSON'.
Assistant: