From intentracker
Detects user directives shifting project goals, scope, approach, or constraints (e.g., CLI to web app) and flags for intent reconciliation. Auto-activates on direction changes.
How this skill is triggered — by the user, by Claude, or both
Slash command
/intentracker:intentrackerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
When the user gives a directive that changes the direction of
When the user gives a directive that changes the direction of the project (not just a specific code task, but a change in goals, scope, approach, or constraints), note this internally and ensure it will be captured at the next intent reconciliation.
Examples of direction-changing statements:
Examples of statements that are NOT direction changes:
When you detect a direction change, you may proactively confirm:
"Got it -- I'll update the project intent to reflect [change].
You can review it anytime with /intent:show."
npx claudepluginhub antfu/intentracker --plugin intentrackerEnforces a planning gate before code changes: investigate context, surface blockers, produce a step-by-step plan, and implement only after explicit approval.
Clarifies vague or ambiguous user requests by exploring the codebase first, then running an iterative Q&A loop until scope is clear.
Creates a Locked Intent Boundary artifact to fix human intent before planning, preventing agents from redefining goals. Use before any build/remove/replace/migrate/refactor task or when turning discussion into a master PRD.