Eisenhower Four-Quadrant Task Manager

Problem

This skill addresses “state drift” in Markdown task lists: customer projects, personal execution, delegation, and backlog ideas can scatter across files, making it hard to tell what must be handled today versus what is optional. It keeps data in a small set of files under tasks/, with customer-projects.md as the single source of truth for customer projects.

How It Works

• Four-quadrant execution: tasks.md records tasks that require your own execution in Q1, Q2, Q3, and Q4, with P0, P1, and P2 priority labels.
• Renumbering checks: after adding, completing, or archiving, it scans for duplicates, gaps, and misplaced order, then reassigns numbers from 1 and verifies again.
• Dashboard view: the optional dashboard/ uses Node.js to parse Markdown in real time and push changes over WebSocket, which is useful for reviewing the matrix, customer projects, delegation list, and Maybe ideas.

Fit and Limits

It suits individuals or small teams running an operations cadence: review Q1 and customer escalations daily, plan Q2 weekly, and clean up archives monthly. If you need concurrent multi-user writes, permission auditing, complex dependency tracking, or cross-system task synchronization, treat it as a local task view rather than the only project database.