track

name	track
description	Track and view the job-application pipeline (saved, applied, interviewing, offer). Use when the user wants to save a job, update its status, add a note, or see their pipeline, e.g. "/jobfinder:track applied adzuna:12345" or "/jobfinder:track list".

jobfinder: track

Manage the application pipeline. $ARGUMENTS is a free-text instruction — map it to the right tracker.py subcommand.

Command mapping

Run uv run "${CLAUDE_PLUGIN_ROOT}/scripts/tracker.py" <subcommand>:

User intent	Subcommand
save / bookmark a job	save <id>
mark applied	applied <id>
moving to interview	interviewing <id>
got an offer	offer <id>
rejected / passed	rejected <id>
hide it	archived <id>
add a note / reminder	note <id> <text...>
show one job + history	show <id>
see the pipeline	list (add --status <status> to filter)

Valid statuses: seen, saved, applied, interviewing, offer, rejected, archived.

Presenting the pipeline

For list, render the results grouped by stage in a sensible order (saved → applied → interviewing → offer, with rejected/archived last). For each job show title, company, AU location, AUD salary, id, and days since last update.

Add gentle, useful nudges based on updated_at, e.g. "applied 14 days ago — consider a follow-up" or "interview logged 3 days ago — send a thank-you note?". Keep it brief; don't badger.

If a job id isn't found, the user probably needs to /jobfinder:search for it first (searching stores listings automatically), or you can add it with tracker.py add.