> For the complete documentation index, see [llms.txt](https://onevarez.gitbook.io/cli/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://onevarez.gitbook.io/cli/concepts-1/build-tasks.md).

# Build tasks

Build tasks are the fuel that propels Laraboot. A build task is a small piece of logic that is sequentially called at its own time and performs an operation against or based on the status of the workspace and the project configuration.

There are two types of build tasks, [core](/cli/concepts-1/build-tasks/core-tasks.md), and [community](/cli/concepts-1/build-tasks/community-tasks.md). The latter sits over the former.

### Adding a build task to the project

Build tasks can be added via CLI using the `task add` command which has the following structure:

```
laraboot task add <name> [options]
```

### Core build tasks

[Core tasks](/cli/concepts-1/build-tasks/core-tasks.md) can be added by specifying their name.

```bash
# For instance
laraboot task add @core/laravel-foundation-provider --format=file
```

### Community build tasks

These tasks do not form part of the core and are maintained by the community.

Community tasks can be added by specifying their name and id. This information is often found on the build task homepage.

```bash
# For instance
laraboot task add hello-task --buildTaskID xxxxxxxx
```