> For the complete documentation index, see [llms.txt](https://sp.jerrygems.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sp.jerrygems.tech/volume-iv-the-indicative-engine-and-verb-conjugation/31-the-compound-tenses-with-haber.md).

# 31. The Compound Tenses with Auxiliar HABER

> *The 5 compound tenses: Present Perfect, Pluperfect, Preterite Anterior, and beyond.*

***

## The Perfect Tenses Engine

In Spanish compound tenses, you **NEVER use&#x20;*****tener***. You strictly conjugate the helping verb **HABER**, and the participle (*-ado / -ido*) **STAYS FROZEN IN -O**:

* **Present Perfect (Pretérito Perfecto):** *he, has, ha, hemos, habéis, han* + *comido*
  * *«Hoy **he comido** con mis padres.»* (Today I have eaten with my parents.)
* **Pluperfect (Pluscuamperfecto):** *había, habías, había...* + *comido*
  * *«Cuando llegué a la estación, el tren ya **se había marchado**.»* (When I arrived, the train had already left.)
* **Preterite Anterior (Hubo comido):** High literary register for immediate anteriority:
  * *«Apenas **hubo terminado** el discurso, todos aplaudieron.»* (As soon as he had finished the speech, everyone applauded.)


---

# 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://sp.jerrygems.tech/volume-iv-the-indicative-engine-and-verb-conjugation/31-the-compound-tenses-with-haber.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.
