Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/FranksGP/Gestor_de_tareas/llms.txt

Use this file to discover all available pages before exploring further.

Adding a task is the core action in Gestor de Tareas. When you select option 1 from the main menu, the application prompts you for a title and a description, then immediately persists the new task to Tareas.json with a status of Pending. Every task you create follows this same structure, making it straightforward to manage your list over time.

​
Workflow

1

Run the application

Open a terminal in the directory that contains index.py and start the program:
python index.py
The main menu is displayed:
Gestor de Tareas
1. Agregar tarea
2. Listar tareas
3. Marcar tarea como completada
4. Eliminar tarea
5. Salir
2

Select option 1

At the prompt, type 1 and press Enter:
Seleccione una opción: 1
3

Enter a title

The application asks for the task title. Type a short, descriptive name and press Enter:
Título de la tarea: Comprar leche
4

Enter a description

The application then asks for a description. Provide any additional context and press Enter:
Descripción de la tarea: Ir al supermercado
A confirmation message is printed immediately:
Tarea agregada exitosamente.

​
Full terminal example

The complete interaction for adding a single task looks like this: 
Gestor de Tareas
1. Agregar tarea
2. Listar tareas
3. Marcar tarea como completada
4. Eliminar tarea
5. Salir
Seleccione una opción: 1
Título de la tarea: Comprar leche
Descripción de la tarea: Ir al supermercado
Tarea agregada exitosamente.

​
What happens internally

When you confirm your input, the application executes the following chain:
  1. agregarTask(titulo, descripcion) is called with the values you entered. It loads the current task list from disk via cargarTask(), appends a new dictionary to the list, and then calls guardarTask(tasks).
  2. guardarTask(tasks) opens Tareas.json in write mode and serialises the entire updated list back to disk using json.dump with an indent of 4 spaces.
This means your task is durably saved before the menu is displayed again — there is no separate “save” step.

​
Resulting JSON structure

After adding the example task above, Tareas.json will contain: 
[
    {
        "titulo": "Comprar leche",
        "descripcion": "Ir al supermercado",
        "completed": false
    }
]
Each entry in the array represents one task. Additional tasks are appended as further objects in the same array.
Every task created through option 1 always starts with "completed": false. There is no way to add a task that is already marked as completed from the menu — the initial status is set unconditionally inside agregarTask.
Choose descriptive, unique titles for your tasks. The title is the primary identifier shown when you list, complete, or delete tasks. A clear title like "Comprar leche" is much easier to locate at a glance than a generic one like "Tarea 1".

Build docs developers (and LLMs) love

Get started for freeTalk to us