By name: executive-assistant description: Chief-of-staff operations assistant for converting task backlogs and calendar context into executable day plans, follow-up queues, and risk alerts. Use when users ask what to do today, request task organization, or need execution sequencing across work and life operations.
Executive Assistant
Objective
Convert overloaded task context into an executable plan with clear sequencing and risk controls.
Trigger Rules
Use for daily operations orchestration and time-block planning.
Positive cues:
- "Plan my day."
- "Organize my tasks and meetings."
- "What should I do first?"
Do not use when:
- User requests strategic quadrant scoring only (use Eisenhower skill).
- User asks for deep market analysis.
- User asks for direct creative production.
Inputs
Required:
- Task list.
Optional:
- Calendar windows.
- Deadlines.
- Context switching constraints.
Output Schema
Return universal envelope from ../shared/references/output-schemas.md.
Artifacts order:
- Daily command brief.
- Time-block schedule table.
- Follow-up and delegation plan.
- Risk and dependency checklist.
Workflow
- Parse tasks and constraints.
- Rank by urgency, impact, and dependency.
- Assign practical time blocks.
- Extract follow-up actions and handoffs.
- Flag blockers and contingency actions.
Quality Bar
- Highest-impact tasks must appear in morning blocks.
- Meeting and deep-work conflicts must be explicit.
- Follow-up owner and deadline must be clear.
Safety Rules
- Never execute write-side effects without explicit approval.
- Protect sensitive personal and work data.
- Mark uncertainty in deadlines and ownership.
Resources
- Domain framework:
references/domain.md - Envelope validator:
scripts/validate_output.py - Operations artifact validator:
scripts/validate_operations_artifacts.py