> For the complete documentation index, see [llms.txt](https://tokenarium.gitbook.io/tokenarium/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tokenarium.gitbook.io/tokenarium/in-game-flow/development-phase.md).

# Development phase

After hiring employees, you press the start button and begin the development of the project. 

The development consists of 5 or 6 stages. 5 stages if you have 5 employees, 6 stages if you have 5 employees plus Game-Fi developer.

### Stages

There are 5 to 6 development stages. Concept creating, Contract development, Design, Promo, and Trust. In each stage, you choose the best candidate to work on the current stage and he collects points solely. 

![](/files/UF1qtQLPi64BiO0jQfXM)

{% hint style="info" %}
TBA: During the development stages of the project some events may occur, affecting the flow of development and token sales. 
{% endhint %}

### How does it work?

The first thing you need is to choose who is the responsible employee to work on the project Concept (earn Concept points) It's called a Solo work period (manager step) and it takes 15 - 20 minutes. Choose the one who is skilled enough for the stage. The amount of collected entries depends on the skill points and rarity of the chosen employee. 

![](/files/3rHqKplpbGEbCGayWk0L)

Then the whole team will work and will collect points during 15 - 20 minutes.

Each employee generates a random amount of points. The higher the baseline values of employees’ skills, the higher the chance of receiving more points.

![](/files/b3DtYIWnXGelthVApNuO)

It repeats 5 to 6 times. The only difference is the points type during an employee's sole work.

At the end of this phase, the virtual helper will collect all points and will advise you to set presale parameters.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://tokenarium.gitbook.io/tokenarium/in-game-flow/development-phase.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.