eisenhower-priority-ai
npx machina-cli add skill cloudaipro/openclaw-agent-skills/eisenhower-priority-ai --openclawEisenhower Priority AI
Objective
Transform unstructured task lists into quadrant-based execution order with explicit tradeoffs.
Trigger Rules
Use when users need prioritization clarity, not calendar orchestration.
Positive cues:
- "I have too many tasks."
- "Help me prioritize now."
- "Use Eisenhower matrix."
Do not use when:
- User asks for full day scheduling (use executive-assistant).
- User asks for course or marketing design.
- User asks for research-only persona analysis.
Inputs
Required:
- Task list.
Optional:
- Deadlines.
- Impact metrics.
- Owner/dependency notes.
Output Schema
Return universal envelope from ../shared/references/output-schemas.md.
Artifacts order:
- Prioritization summary brief.
- Quadrant classification table.
- 50/40/5/5 action plan.
- Anti-overload checklist.
Workflow
- Score urgency and importance signals.
- Place tasks into Q1/Q2/Q3/Q4.
- Rank tasks within each quadrant.
- Allocate effort using 50/40/5/5 split.
- Return execute/delegate/drop recommendations.
Quality Bar
- Classification rationale must be visible.
- Q2 strategic tasks must not be crowded out.
- Q4 tasks should default to eliminate/defer.
Safety Rules
- Avoid fabricated deadlines.
- Mark assumptions where metadata is missing.
- Keep recommendations actionable and reversible.
Resources
- Domain framework:
references/domain.md - Envelope validator:
scripts/validate_output.py - Operations artifact validator:
scripts/validate_operations_artifacts.py
Source
git clone https://github.com/cloudaipro/openclaw-agent-skills/blob/main/skills/eisenhower-priority-ai/SKILL.mdView on GitHub Overview
Transforms an unstructured task list into a quadrant-based execution order using urgency and importance signals. It outputs a 50/40/5/5 action allocation to clarify what to do, what to delegate, and what to drop, helping overloaded users regain decisiveness with rationale.
How This Skill Works
The engine scores urgency and importance, buckets tasks into Q1 through Q4, ranks items within each quadrant, then allocates effort using a 50/40/5/5 split and returns recommendations for execute, delegate, or drop. Optional inputs like deadlines, impact metrics, and owner notes refine the classification and tradeoffs.
When to Use It
- I have too many tasks and no clear execution order.
- I need a decisive execution order with rationale for what to do next.
- I want to ensure high-impact work (Q2) isn’t crowded out by urgent but lower-impact items.
- I want explicit tradeoffs and clear ownership (who/what gets done by when).
- I want to reduce overload quickly by knowing what to drop or defer.
Quick Start
- Step 1: Provide your Task list (and optional deadlines, impact metrics, and owner notes).
- Step 2: Run Eisenhower prioritization to classify tasks into Q1–Q4 and compute the 50/40/5/5 allocation.
- Step 3: Review the execute/delegate/drop recommendations and start with the top-priority actions.
Best Practices
- Provide a complete task list with optional deadlines and impact metrics when available.
- If metadata is missing, mark explicit assumptions and proceed with transparent tradeoffs.
- Keep Q2 strategic tasks visible to prevent crowding by urgent items.
- Default to eliminate or defer Q4 tasks to reduce overload.
- Maintain auditable 50/40/5/5 allocations so you can adjust if outcomes differ.
Example Use Cases
- Engineering backlog triage: bugs, features, and refactors with deadlines and impact scores.
- Support-ticket triage: categorize by urgency and business impact with ownership notes.
- Product backlog prioritization: balance technical debt with feature work and dependencies.
- Internal process improvements: automation tasks with owners and cross-team dependencies.
- New-hire onboarding tasks: identify essential steps first to accelerate productivity.
