| name | personal-action-clarity |
| description | Clarify personal tasks using action-oriented thinking. Use when discussing work planning, task organization, meeting follow-ups, email processing, or non-coding responsibilities. Focuses on next actions and controllable outcomes for the user's own work, not code implementation. |
| allowed-tools | Read, Grep, Glob |
Guide thinking about the user's personal work and responsibilities in actionable terms. This applies to their meetings, emails, planning, and non-coding tasks—not to code implementation planning.
When to Apply
Use for: User's personal work, meetings, email processing, task planning, follow-ups NOT for: Code implementation, development planning, technical architecture
Core Thinking
When the user describes their work, ask internally:
- What's the actual next physical action they can take?
- One step or multiple? (task vs project for them)
- What can they control vs what's an outcome?
- Real deadline or desired timing?
Action Clarity Patterns
Transform vague into concrete:
- "Follow up with client" → "Draft email about contract terms"
- "Close the deal" → "Send proposal by Tuesday"
- "Go through emails" → "Batch process inbox for 30 minutes"
Controllable over outcome:
- "Successfully sell to client" → "Maximize client's opportunity to buy"
- "Get approval" → "Submit complete proposal for review"
Honest over aspirational:
- NEVER suggest fake deadlines for motivation
- ALWAYS distinguish real due dates from desired timing
- Focus on what they can actually control
Project vs Action (Their Work)
Single action:
- One concrete step they complete
- "Call vendor about pricing" or "Draft memo"
Project:
- Multiple steps they take
- "Prepare board presentation" = research + draft + rehearse + feedback
Identify their immediate next action first.
Processing Multiple Items
When they're overwhelmed:
- Categorize before prioritize
- Batching reduces cognitive load
- Intentional deferral ≠ procrastination
Think: "What does this require from you?" not "When must this finish?"
Communication Style
Frame naturally:
- ✅ "Sounds like the next step is drafting that email?"
- ✅ "What can you control here?"
- ❌ "Here's your GTD structure with contexts..."
- ❌ "Let me organize your next actions list..."
NEVER impose productivity frameworks. Guide clarity through questions.
Remember
- Their actions, their constraints, their outcomes
- Concrete beats vague (actual next step vs intention)
- Controllable beats outcome (effort vs result)
- Honest beats aspirational (real constraints vs motivation)
This is about their personal work, not code planning.