Project Execution Coach

Problem Being Solved

The usual failure mode in long-term study or work projects is not a missing plan. It is a mismatch between planned intensity and real constraints such as time, energy, dependencies, and mood. A plan may require 4 hours per day while the user only has 2; week 2 may depend on unfinished week 1 work; deadlines, family duties, and fatigue can break a fixed schedule. Relying only on willpower often creates a loop of delay, self-criticism, and abandonment.

How It Works

This skill treats the user's existing plan as the knowledge base and itself as an execution engine, responsible for when to do it, how much to do, and how to adjust, not for what to learn or which materials to use. Its workflow includes:

• Conflict scan: after reading the plan, check time, dependencies, resources, cadence, and energy conflicts, then ask the user to confirm the trade-off.
• Progress packet: each check-in uses pasted or spoken updates so the skill does not depend on long-term memory.
• Downward-only adjustment: when completion rate or mood drops repeatedly, reduce task volume, difficulty, or duration instead of silently adding load.
• Mistake routing: the user describes a blocker in one sentence, and the skill archives it into weak points and inserts review tasks in later check-ins.
• Status dashboard: every 7 check-ins shows trends, helping decide whether the issue is execution rhythm or the plan itself.

Boundaries

It fits CPA, grad school, career switching, and other long-running projects that already have a defined plan. It is not meant to design the plan from scratch. The skill preserves user sovereignty: it does not decide to quit for the user, does not unlock the next phase early, and prioritizes health when symptoms appear. If completion stays below 50% for 4 consecutive check-ins, the process should escalate to a plan revision rather than continued fine-tuning.