# Introduction

Catana is a tool to help **manage and prevent TODOs from turning into technical debt**.

It **enhances developers' annotations with a set of features and conventions**, all while helping project owners **maintain a comprehensive overview of the health of their codebases** across their organization.

Your projects deserve a better alternative than restricting or leaving TODOs growing out of control.

<figure><img src="https://2920834341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvC5eZACoQiLmi7enAypu%2Fuploads%2FAJVnntHErLDiIQQSN9PV%2Fdashboard-design.png?alt=media&#x26;token=9e9a540b-1104-4011-8625-d374d9a13f7d" alt="" width="563"><figcaption></figcaption></figure>

## <mark style="color:blue;">Leaving TODOs unmanaged</mark>

The accumulation of unresolved TODOs **contributes to the long-term maintenance overhead of your projects**. What originally was an innocent TODO could transform into a technical debt, slowing you down at best or even creating a security incident in the worst-case scenario.\
\
Without proper tooling, TODOs are hard to remember for developers, time-consuming to track down for team members, and nearly impossible to manage for project owners.

## <mark style="color:blue;">Restricting TODOs</mark>

In an attempt to tackle the inherent problems associated with writing TODOs, organizations may be tempted to resort to a drastic measure: **restrict TODOs with a linter** before they land on the release branch.

<figure><img src="https://2920834341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvC5eZACoQiLmi7enAypu%2Fuploads%2FPhwCe3vUOhVXbh29wOsG%2Ftodo-linter.png?alt=media&#x26;token=5e51258b-0e9d-48dc-8854-231a9acca538" alt="" width="563"><figcaption></figcaption></figure>

Because a TODO is often insufficiently specific to justify opening an issue, restricting its usage and inciting creating a ticket may **lead developers to take a mental note instead. A mental note is a recipe for catastrophe.**

In large projects with often hundreds of opened tickets, an issue tracker is already difficult to manage. Overloading it with “TODOs converted to issues” will bury them even deeper.

Major software organizations (Google, Cloudflare, Stripe, Shopify…) allow TODOs in their codebases for a reason:  A TODO and an issue tracker have **different uses, and solely using one over the other is not a solution.**

## <mark style="color:blue;">Introducing Catana</mark>

<figure><img src="https://2920834341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvC5eZACoQiLmi7enAypu%2Fuploads%2FbbsVR33C9CTSmZXP548h%2Ftest.png?alt=media&#x26;token=94c99938-80eb-4b08-84b0-b52e78c489f0" alt="" width="563"><figcaption></figcaption></figure>

Catana was designed to solve the three inherent problems of TODOs:&#x20;

* Difficult to remember.
* Hard to find.
* Painful to manage.

Existing and upcoming TODOs on all your projects are recorded with detailed information in the background.

Each TODOs gets assigned ([automatically or manually](https://docs.catana.dev/core-concepts/assigning-todos)) and Catana either **reminds its assignee** discreetly by [email or more loudly when a TODO is actionable](https://docs.catana.dev/core-concepts/regular-and-expiring-todos).

TODOs on all projects across your organization are presented on a **dedicated and comprehensive dashboard**.\
Catana also offers multiple features to save developers’ time and automate tedious tasks.

<br>


---

# Agent Instructions: 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:

```
GET https://docs.catana.dev/overview/readme.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
