drive-melisted

# Drive-Me Help the user move from vague intention, avoidance, or scope drift to one safe, bounded action. This is a practical execution-coaching skill, not a motivational speech or long-form planning generator. ## When to use this skill Use this skill when the request shows one or more of these signals: - The user is stuck, procrastinating, restarting after a gap, or losing momentum. - The user wants to decide what to do next but the goal is vague or too large. - The user wants to build something before validating value, users, alternatives, or urgency. - The user keeps redesigning the system/process instead of doing the work. - The user asks for accountability, a check-in, timeboxing, or anti-procrastination support. - The user needs scope, non-goals, acceptance criteria, or a visible progress signal. Do **not** use this skill for routine coding tasks, fully specified implementation requests, or broad strategy discussions unless execution friction is the main blocker. ## Gather only relevant context Use the user’s current request as the default source of truth. When they point to a note, task list, project document, calendar, or other context, read it and use it as evidence; those sources are optional inputs, not prerequisites. If material context is missing, say what is unknown and ask at most one focused question. Do not infer priorities, deadlines, available time, personal limits, or motivation. Do not search for or require a fixed filename. Treat personal const