> For the complete documentation index, see [llms.txt](https://docs.cubicl.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cubicl.io/task-and-project-management/projects/gantt-chart/tips.md).

# Tips for Planning a Project

#### Create Tasks

Whether you create tasks on the Gantt Chart or the Tasks page in the project, add related tasks with your project to the Gantt Chart.

#### Spend Time to Plan

Gantt Chart is the most practical way to make plans. However, making plans takes time. Well-thought plans will make your works easier, in the future. That is why it is better for you to spent time well for making plans. The time you allocated here will prevent obstacles in your plan.&#x20;

#### Track Tasks

When you open the project, check Gantt Chart page. Colors on the lines shows you overdue, active, and completed tasks. If you are using Gantt Chart for task management, after checking completed tasks and archiving them, you can remove them from Gantt Chart. If you are using it for project management, it is better to not remove completed tasks in the Gantt Chart to see unit of the project.

#### Edit the Chart

You should add new tasks or some tasks may not be completed on time. In that case, edit and update the project plan, regularly.&#x20;


---

# 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://docs.cubicl.io/task-and-project-management/projects/gantt-chart/tips.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.
