markdown-task-manager

📋 Markdown Task Manager Skill

When to Use This Skill

• Create tasks to document work to be done
• Plan complex features
• Track project progress
• Archive completed tasks
• Generate status reports

📋 STRICT Task Format

Mandatory Template

### TASK-XXX | Task title

**Status**: <column-id>
**Priority**: [Critical|High|Medium|Low] | **Category**: [Value] | **Assigned**: @user1, @user2
**Created**: YYYY-MM-DD | **Started**: YYYY-MM-DD | **Due**: YYYY-MM-DD | **Finished**: YYYY-MM-DD
**Tags**: #tag1 #tag2 #tag3

Free text description. **NO `##` or `###` headings allowed**.

**Subtasks**:
- [ ] First subtask
- [x] Completed subtask

**Notes**:
Additional notes with subsections `**Title**:`.

**Result**:
What was done.

**Modified files**:
- file.js (lines 42-58)

❌ FORBIDDEN

• ## Title or ### Title inside a task
• **Subtasks** or **Notes** without :
• Automatic archiving (only on user request)

Why? All tasks share one ## Tasks section, so a stray ##/### heading inside a task can break parsing.

🔄 Workflow

V2 — status is a field, not a position. A task's column is its **Status**: value; all tasks live in one ## Tasks section. Move a task by editing its one **Status**: line — never cut/paste the whole block (~1 line vs 20+).

1. New Request

1. Read kanban.md to get the last task ID
2. Add the task to the ## Tasks section with **Status**: todo (first column id)
3. Unique ID (TASK-XXX) auto-incremented
4. Break down into subtasks if needed
5. Increment counter in <!-- Config: Last Task ID: XXX -->

2. Start Work

1. Edit one line: **Status**: todo → **Status**: in-progress
2. Add **Started**: YYYY-MM-DD
3. Check off subtasks progressively

3. Finish Work

1. Edit one line: **Status**: in-progress → **Status**: done
2. Add **Finished**: YYYY-MM-DD
3. Document in **Notes**::
   • **Result**: - What was done
   • **Modified files**: - List with line numbers
   • **Technical decisions**: - Choices made
   • **Tests performed**: - Validated tests