From aafb0fbde5289a45f9f818a00141f80b149be283 Mon Sep 17 00:00:00 2001
From: Agando <roduccomm@gmail.com>
Date: Tue, 2 Jun 2026 18:00:37 +0200
Subject: auto: 2026-06-02_18:00 changes

---
 skills/task-manager.md | 37 +++++++++++++++++++++++++++++++++++++
 1 file changed, 37 insertions(+)
 create mode 100644 skills/task-manager.md

(limited to 'skills/task-manager.md')

diff --git a/skills/task-manager.md b/skills/task-manager.md
new file mode 100644
index 0000000..74c3da1
--- /dev/null
+++ b/skills/task-manager.md
@@ -0,0 +1,37 @@
+---
+name: task-manager
+description: A systematic approach to managing tasks using a JSON-based tracking system in the VFS.
+tags: productivity, management, organization
+---
+
+# Task Management Workflow
+
+## 1. Initialization
+- Check if `/tasks.json` exists. If not, create it with an empty array: `[]`.
+
+## 2. Adding Tasks
+When a new task is identified:
+- **Define**: Task name, priority (Low, Medium, High), status (Todo, In-Progress, Done), and deadline.
+- **Action**: Read `tasks.json`, append the new task object, and write back to the file.
+
+## 3. Daily Planning/Review
+- **List**: Read `tasks.json` and filter for "Todo" or "In-Progress".
+- **Prioritize**: Sort tasks by priority (High > Medium > Low).
+- **Update**: Change status of tasks as they are completed.
+
+## 4. Maintenance
+- **Cleanup**: Archive "Done" tasks to `/tasks_archive.json` periodically to keep the main list lean.
+- **Audit**: Review overdue tasks and update deadlines or priorities.
+
+## Schema Reference
+```json
+{
+  "id": "unique-id",
+  "title": "Task name",
+  "priority": "High|Medium|Low",
+  "status": "Todo|In-Progress|Done",
+  "created_at": "ISO-Date",
+  "deadline": "ISO-Date",
+  "notes": "Additional context"
+}
+```
\ No newline at end of file
-- 
cgit v1.2.3