--- name: track-pipeline description: Maintains a DS/CS student's job-search pipeline for internships, co-op, and new-grad SWE / data science / ML roles in profile/tracker.md: application statuses, interviews, follow-up dates, events proposed by check-inbox and debrief, and a weekly digest. Use when the user asks to log an application or a sent message, update a status, see what's due, apply pending events, or get a weekly summary. --- # track-pipeline ## Files - `profile/tracker.md` (create from `resources/tracker.template.md`): Roles, Interviews, Events, digest. - Reads `profile/roles.md`, `profile/contacts.md`, `profile/connect-queue.md`. - Application status lives on the Roles row; connection/contact state lives in `contacts.md` and the queue. They link by `role_id`. ## Statuses (Roles) `shortlisted → tailored → applied → oa → interview → offer | rejected | ghosted | withdrawn | skipped` Outreach and invites are not statuses: they are recorded in `contacts.md` (`relationship`) and noted in the row's `contacts` and `next_action`. ## Steps 1. **Add** from `find-roles` / `score-fit`: one Roles row per role_id (status `shortlisted`), dedupe by role_id. 2. **Record what the user reports** (applied, emailed, met, interviewed): update status, `last_touch` = today, and `next_action` + `due`: - applied → follow up after `follow_up_after_days` (default 7). - invite sent → `contacts.md` relationship `connect_sent `; next action "check acceptance in LinkedIn" in 7 days. - interview → add an Interviews row; prep 2 days before; thank-you draft the same day; after it happens, set `completed_on` + `completed_source` (user said / debrief / calendar) and `expected_response_by` = the date they promised, else `completed_on` + `inbox.no_response_weekdays` weekdays. 3. **Apply events.** For each Events row in state `pending` (from `check-inbox` or `debrief`): apply it if it is unambiguous and newer than the row's last change; otherwise ask. Set the event's state to `applied` or `rejected`. An older event never overwrites newer progress. 4. **Artifacts.** Fill `resume` or report paths only after confirming the file exists at that path. 5. **Due today:** rows and Interviews with `due` or `expected_response_by` ≤ today, sorted by date, each with the next skill (e.g. `draft-outreach` follow-up). 6. **Weekly digest** (on request or Mondays): counts per status, new this week, applications, invites sent (from `connect-queue.md`), replies, response rate, upcoming OAs/interviews, overdue responses, top 3 actions. 7. Write changes and show a short diff. ## Rules - Something counts as applied or sent only on evidence: the user's report, `linkedin-browser`'s `sent` rows, or an `application_received` email matched to the role by requisition id or thread (`check-inbox`), recorded with the email's date and `gmail:` source. A confirmation matched by company alone stays `pending` for the user to confirm. - Dates ISO `YYYY-MM-DD`. Rows are never deleted; use `withdrawn` / `skipped`.