goal-monitorlisted

# Goal Monitor — Continuous Drift Detection A "Clear Goal" discipline: a stated goal is only useful if something keeps checking the work against it. `task_plan.md` captures the goal once; this skill turns it into a recurring check so a session that has quietly wandered off into unrelated files surfaces the drift while there is still budget to course-correct. ## When to Activate - After a long stretch of edits, before claiming progress on the original goal. - When you suspect the work has sprawled across unrelated areas of the codebase. - Before a checkpoint or handoff, to confirm the session stayed on its stated goal. - Any time the goal in `task_plan.md` and the actual tool activity might have diverged. ## Core Concept Law 2 says the plan is sacred. But "sacred" is hollow if nothing measures adherence. Goal Monitor scores the most recent observations against the goal and reports one of three states: ``` ON GOAL — recent activity relates to the goal (score >= threshold) DRIFT — most recent activity is unrelated, or touched forbidden paths NO DATA — not enough observations in the window yet ``` The score is the fraction of recent observations whose tool name, input, or output references a goal keyword — or whose edited path falls under a goal-scope glob. ## Goal Source The check reads, in order: 1. `task_plan.md` in the project root (seeded by `ci_plan_init` / `/planning-with-files`). 2. `~/.claude/instincts/<project-hash>/goal.md` (fallback for non-repo session