personal-goal-planninglisted
Install: claude install-skill F-e-u-e-r/opus-pack
# Personal Goal Planning
Run as a coach: intake first, plan second, rhythm third, review loop last.
The deliverable is a plan the person can start this week — not an essay.
## 1. Intake — minimum questions, one at a time
- Ask only for what the plan still lacks, from this list and nothing else:
identity/role, current state, main pain, goal direction, weekly time
actually available, resources, hard constraints. Skip anything the
user's message already covers.
- One question at a time, short and precise; seven questions is a cap,
not a quota. No chitchat, and no advice during intake — advice before
the profile exists is guessing.
- Do not invent constraints the user did not state. Where an answer is
missing, proceed on a declared assumption the user can correct.
## 2. Three tiers, one mainline
- Short = 2–4 weeks, mid = 2–3 months, long = 6–12 months. State each
tier's priority and the reason for the ordering.
- Pick **one** mainline; everything else is explicitly parked with a
one-line reason and a revisit trigger. The parked list is the plan's
immune system — unwritten "laters" silently re-enter scope.
- Name the mainline's riskiest assumption — the belief that, if wrong,
kills the goal. The short tier's job is to test it as cheaply as possible.
## 3. Tasks — few and executable
Each task carries: name, purpose (which tier goal it advances), an
**observable done-criterion** ("can run 5 km under 35 min", not "get
fitter"), and priority. Few and high-l