Gestor de Tareas is a working, fully functional task manager, and the README already points toward where the project is headed next. The current command-line interface is a solid foundation — tasks persist between sessions in a JSON file, the menu is straightforward to navigate, and the codebase is small enough for any contributor to understand in a single sitting. The planned improvements listed below build on that foundation rather than replacing it, adding the features that would make Gestor de Tareas useful beyond a university workshop setting.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.
Planned features
Graphical Interface (GUI)
Replace the numbered console menu with a proper desktop GUI — Tkinter is the natural first choice since it ships with Python and requires no extra dependencies. A web-based UI (for example with Flask) is another option worth exploring. Either approach would make the application accessible to users who are not comfortable working in a terminal.
Due Dates
Add an optional deadline field to every task so users can record when something needs to be done. Once dates are stored, the list view could sort or filter tasks by urgency — for example showing overdue items at the top — making it much easier to prioritise work at a glance.
Categories & Labels
Introduce a tagging or category system so tasks can be grouped by project, area of life, or custom priority level. A task could belong to
trabajo, personal, or estudio, and the list view could be filtered to show only the relevant group, keeping the interface focused and uncluttered.Remote Sync
Persist tasks to a remote database — SQLite over a shared drive for simple cases, or a cloud service for full multi-device access. This would allow the same task list to be used from multiple machines and would make accidental file deletion far less catastrophic than it currently is.
Current limitations
The items below are known constraints of the current implementation. They are not bugs — the program works exactly as designed — but they are worth understanding before building on top of the existing code.No undo / un-complete
No undo / un-complete
Once
tareaCompletada() marks a task as "completed": true, there is no menu option to revert it to pending. The only workaround is to edit Tareas.json directly in a text editor. A future version should add an “un-complete” option, or a full undo history, to the main menu.Single flat file storage
Single flat file storage
All tasks live in one flat JSON list inside
Tareas.json. There is no concept of multiple lists, projects, or workspaces. Every task appears in the same view, which becomes unwieldy as the list grows. The planned categories feature would address this, but the storage format would also need to evolve to support it.No search or filter
No search or filter
listarTask() always prints every task in the file. There is no way to search by keyword, filter by completion status, or show only tasks matching a given title fragment. For a short list this is fine; for a list of thirty or more items it becomes impractical. A simple keyword filter would be a low-effort improvement with a high usability payoff.Sequential re-indexing on delete
Sequential re-indexing on delete
Tasks are stored in a Python list and accessed by their position in that list. When
delete_task() removes an entry with list.pop(), every task that followed it shifts down by one index. This means the numbers shown in listarTask() can change between operations, which could confuse users who remember a task’s number from a previous listing.How to propose a feature
If you have an idea that is not listed here — or if you want to take ownership of one of the planned features above — the best first step is to open a GitHub Issue. Describe what you want to build, why it would be useful, and roughly how you imagine it fitting into the existing code. The maintainers and other contributors can then weigh in before anyone writes a line of code, which keeps effort aligned and avoids duplicated work. Open an issue at: https://github.com/FranksGP/Gestor_de_tareas/issuesGestor de Tareas was created as a university Python and Git workshop project by Jorge Hernández, Dissel Leal, and Frank Garzón. The project was designed to practise collaborative development with Git and GitHub as much as it was designed to produce a working application — which is why clean commit history and pull-request etiquette are part of its contributing culture.