track-timer

Track a running timer in Lucen Track

This skill handles the live timer lifecycle: start, stop, and check status. Stopping a timer automatically saves it as a time entry — do not also call create-time-entry.

Decide which branch applies

Detect intent from what the user said.

Start ("start a timer on X", "I'm starting work on the redesign")

1. Resolve the project + phase.
   • If the user mentioned a ticket / issue / branch identifier (e.g. PROJ-123, feature/login-bug, a Linear or Jira key), call search-todos first. A match returns the project and phase.
   • Otherwise call get-projects and pick the project + phase that matches. If multiple plausible matches exist, ask before starting.
2. Resolve any tags with search-tags if the user mentioned them.
3. Call start-timer with the resolved project, phase, optional todo, optional tag ids, and optional note.

Stop ("stop the timer", "I'm done", "stop it")

1. Call stop-timer. This automatically saves the elapsed time as an entry. Do not also call create-time-entry — that would duplicate.
2. Report the saved entry back: project, duration, any note.

Check ("is my timer still on?", "what am I tracking?")

1. Call get-active-timer.
2. If a timer is running, report the project, phase, and elapsed time. If nothing is running, say so plainly — do not start one.

Rules

• Never fabricate project, phase, todo, or tag IDs. Always resolve via search-todos, get-projects, or search-tags first.
• If the user is vague ("start a timer on the website thing"), list candidates from get-projects and ask before starting.
• After stop-timer, never call create-time-entry for the same work — stop already saved the entry.
• If a tool returns an authentication error, tell the user they may need to re-authorize the Lucen Track connector — do not retry repeatedly.

Do not

• Do not modify an existing entry from this skill. For corrections, route the user to /fix-entry.
• Do not generate reports from this skill. For totals or breakdowns, route to /time-report.