> For the complete documentation index, see [llms.txt](https://docs.tabiya.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tabiya.org/tabiya-documentation/es/nuestra-pila-tecnologica/compass/roadmap.md).

# Hoja de ruta

Nuestra visión para Compass incluye:

* ***Mayor alcance geográfico:*** Adopción generalizada de Compass para su uso en mercados emergentes
* ***Soporte multilingüe:*** Ampliar las capacidades lingüísticas para atender a poblaciones diversas
* ***Integración de voz:*** Permitir que nuestros usuarios hablen con Compass en sus dialectos locales
* ***Cartera portátil de habilidades:*** Resultados de exploración de habilidades de Compass activados en una cartera de habilidades interoperable
* ***Funciones mejoradas:*** Desarrollar recomendaciones más avanzadas de trayectoria profesional y desarrollo de habilidades
* ***Capacidades de integración:*** Crear API y herramientas para una integración fluida con las plataformas de empleo y servicios de carrera existentes
* ***Medición del impacto:*** Implementar un ensayo controlado aleatorizado multilateral para estimar el impacto de Compass en los resultados profesionales


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.tabiya.org/tabiya-documentation/es/nuestra-pila-tecnologica/compass/roadmap.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.