Eisenhower Matrix prioritization categorizing tasks by urgency and importance into Do, Schedule, Delegate, Eliminate quadrants. Use for task prioritization, time management, or when overwhelmed.
npx skills add https://github.com/neurofoo/agent-skills --skill eisenhower
Categorize tasks by urgency and importance to clarify what to do, schedule, delegate, or eliminate.
Take the list of tasks provided and sort them into the four quadrants. Be honest about what's truly important (moves you toward goals) versus just urgent (feels pressing but may not matter).
Context
What role/area are we prioritizing for? What's the time horizon?
The Matrix
URGENT NOT URGENT
┌─────────────────┬─────────────────┐
IMPORTANT │ Q1: DO │ Q2: SCHEDULE │
│ │ │
├─────────────────┼─────────────────┤
NOT IMPORTANT │ Q3: DELEGATE │ Q4: ELIMINATE │
│ │ │
└─────────────────┴─────────────────┘
*Handle these immediately—real deadlines, crises, problems*
| Task | Why Urgent? | Why Important? | Do By |
|------|-------------|----------------|-------|
| [task] | [urgency] | [importance] | [when] |
*Block time for these—they don't scream but they matter most*
| Task | Why Important? | Schedule For | Time Needed |
|------|----------------|--------------|-------------|
| [task] | [importance] | [when] | [duration] |
*Someone else can do these—or reduce their urgency*
| Task | Why Urgent? | Who Can Handle? | Delegation Plan |
|------|-------------|-----------------|-----------------|
| [task] | [urgency] | [who] | [how] |
*Stop doing these—or radically reduce time spent*
| Task | Why Are You Doing This? | Elimination Strategy |
|------|-------------------------|---------------------|
| [task] | [reason] | [how to stop] |
Time Distribution Analysis
| Quadrant | % of Time | Ideal % |
|----------|-----------|---------|
| Q1: Do | X% | 20-25% |
| Q2: Schedule | X% | 60-70% |
| Q3: Delegate | X% | 10-15% |
| Q4: Eliminate | X% | <5% |
First Actions
$ARGUMENTS
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Take neurofoo/eisenhower from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.