ai-job-search-cn: Command for Claude Code

/outcome - Record the Result of an Application

You are recording what happened to a job application: progress updates (interview invitations, stages completed, offers) and final resolutions (hired, rejected, no response). The data lands in two places the framework already reads but nothing systematically writes:

• job_search_tracker.csv - the status column that /scrape and /rank use for dedup and exclusion
• documents/applications/<company>_<role>/ - the per-application archive (posting, submitted drafts, outcome.md) that /setup Path A mines to calibrate 04-job-evaluation.md and surface STAR candidates

/outcome writes the data; /setup interprets it. This command never edits the evaluation framework or profile files itself.

The command also owns the stretch before there is an outcome to record: the follow-up branch (Step 2b) surfaces open applications that have gone quiet, drafts a brief follow-up note in the user's voice, and logs it - so the chase and the resolution it eventually leads to live in one flow.

Follow these steps in order.

---

Step 0: Parse Input

$ARGUMENTS may contain:

• Nothing → list open applications and ask which one to update
• A company name (optionally with a role), e.g. /outcome acme or /outcome acme ml engineer → target that application
• followup → enter the follow-up branch (Step 2b) over every quiet open application, using the default threshold of 10 days
• followup <N>, e.g. /outcome followup 14 → follow-up branch with an N-day threshold
• followup <company>, e.g. /outcome followup acme → draft a follow-up for that application now, regardless of threshold
• stale or sweep → enter the stale application sweep branch (Step 2c) over open applications quiet for 60+ days
• stale <N> or sweep <N>, e.g. /outcome stale 90 → stale sweep branch with an N-day threshold

---

Step 1: Load State and Identify the Application

1. Read job_search_tracker.csv. If it does not exist, create it with the standard header:

   date,company,sector,role,role_type,channel,status,contact_person,fit_rating,notes,cv_file,cover_letter_file,source,deadline
   

   If the file exists and its header does not end in ,deadline, append ,deadline to the header line only - no data row is touched. Legacy rows then read as an empty deadline. This is the one edit to an existing tracker this command may make outside a matched row, and Step 4's "never restructure the CSV" governs that row, not this header line.
2. With an argument: match rows case-insensitively on company (and role, if given). One match → proceed. Several → list them and ask. None → the application was made outside the workflow; collect company, role, date applied, channel, and posting URL from the user and add a tracker row.
3. Without an argument: list all rows whose status is not final (see Tracker status vocabulary below) as a numbered table (company, role, date applied, current status, deadline, days quiet, follow-ups sent) and ask which to update. The two derived columns come straight from existing data: days quiet counts from the row's date or the latest dated entry in notes, whichever is more recent; follow-ups sent counts the followed up YYYY-MM-DD markers in notes. If any open row is 10+ days quiet with fewer than two follow-ups sent, add one line under the table: "Some of these have gone quiet - want a follow-up draft? (Step 2b)". If any open rows are 60+ days quiet, also offer: "You have applications quiet for 60+ days — run /outcome stale to batch-resolve them (Step 2c)." If every row is resolved, say so and stop.