Add kate-career-coach to partner-built

partner-built/kate-career-coach/.claude-plugin/plugin.json

@@ -0,0 +1,16 @@
+{
+  "name": "kate-career-coach",
+  "version": "0.3.1",
+  "description": "Kate, a senior career coach for executive job searches. Structured workflows for fit assessment, interview prep, resume optimization, post-interview debrief, and weekly monitoring of target companies and open roles.",
+  "author": {
+    "name": "Chris Bell"
+  },
+  "keywords": [
+    "career",
+    "coaching",
+    "job search",
+    "interview",
+    "executive",
+    "resume"
+  ]
+}

partner-built/kate-career-coach/CHANGELOG.md

@@ -0,0 +1,76 @@
+# Kate — Changelog
+
+---
+
+## v0.3.1 — 2026-03-15
+
+### Internal improvements
+
+**Reduced context load**
+Commands are now thin dispatchers. Each command file collects the context it needs, then defers entirely to `references/flows.md` for execution. Previously, command files restated their flow steps in full and also cited flows.md — redundant in both directions. No change to behavior; lower token cost per command invocation.
+
+**flows.md read once per session, not per command**
+Session initialization now reads `references/flows.md` at startup and holds it in context for the full session. Previously it was re-read on each command invocation. Multi-command sessions (e.g., fit assessment followed by interview prep in the same session) no longer read the file twice.
+
+**Scheduled task prompt generated as a file**
+`/setup-monitoring` no longer embeds the monitoring flow steps directly in the scheduled task prompt. Instead, Kate generates `monitoring/scheduled_task_prompt.md` during setup — a standalone file that the scheduled task reads at runtime. This makes flows.md the single source of truth for monitoring behavior. If you update the monitoring flow in a future version, re-running `/setup-monitoring` regenerates the prompt file automatically.
+
+**Standing coaching rules trimmed**
+Three rules in the coaching rule set (complement skill identification, show don't tell probe, red flag management) were written at execution-instruction detail level — duplicating what flows.md already specifies. They are now principle statements, with execution detail owned exclusively by flows.md.
+
+### What changed
+- All five command files — stripped restated flow steps, kept context-gathering
+- `SKILL.md` — flows.md added to Session Init Step 1; three Standing Coaching Rules reduced to principle statements
+- `commands/setup-monitoring.md` — embedded scheduled task prompt replaced with generated-file approach
+
+---
+
+## v0.3.0 — 2026-03-05
+
+### New coaching capabilities
+
+**Complement skill identification**
+Kate now identifies the specific capability each target organization lacks that the candidate uniquely brings — in one sentence, at every fit assessment. This becomes the positioning anchor for all downstream resume and interview prep. Kate flags any positioning language that tries to mirror the company's existing strengths rather than filling their gaps.
+
+**Non-negotiable difference**
+Kate now probes for the one thing a candidate's next role must have that their current one didn't. This question is introduced in onboarding and revisited any time a search stalls or drifts. Vague or shifting answers are treated as a search-clarity problem, not a market problem. The answer is stored alongside the motivation profile and used as a hard filter in every fit assessment.
+
+**Show don't tell probe**
+As part of interview prep, Kate now identifies the company's 1-2 core challenges and asks whether the candidate has prior work — a framework, analysis, strategy doc, prototype, or decision artifact — that speaks directly to one of them. If they do, Kate helps shape how to present it and surface it naturally in the conversation. If they don't, prep continues as normal. Includes a confidentiality flag for work products from current or recent employers.
+
+### What changed
+- `SKILL.md` — three new Standing Coaching Rules added
+- `references/flows.md` — non-negotiable difference probe added to Onboarding Step 2; complement skill identification added to Fit Assessment Flow; Section 2B added to Pre-Interview Prep Flow
+
+---
+
+## v0.2.2 — prior release
+
+### Core capabilities
+
+**Onboarding**
+Builds a complete user profile from resume and LinkedIn in a single session. Covers target roles and level, domain preferences, company stage and type, compensation (including equity structure), search constraints, and motivation. Includes automatic sweep for prior call transcripts via Granola. Produces a candid positioning read before the search begins.
+
+**Fit assessment** (`/fit-assessment`)
+Evaluates a job description against the user profile and produces a Fit Tier classification (Target / Stretch / Reach), the two or three strongest fit signals, and the key gaps. Acts as a go/no-go gate before any resume or prep work begins.
+
+**Resume optimization**
+Side-by-side resume editing with explicit justification for every proposed change. Rules applied consistently: graduation year handling, personal section flagging, formatting preservation, vocabulary alignment to the JD, and overclaiming prevention.
+
+**Interview prep** (`/interview-prep`)
+Structured prep brief covering interviewer research, company intel, user positioning, talking points mapped to JD requirements, anticipated tough questions (with interviewer motivation, not just suggested answers), red flags to address proactively, and prioritized questions to ask. Includes a clean call notes document formatted for use during the actual call.
+
+**Transcript capture**
+Retrieves and files call transcripts after recruiter and interviewer calls. Integrates with Granola for automatic retrieval, or accepts manual paste or file upload. Consistent filename convention and metadata header applied to all transcripts.
+
+**Post-interview debrief** (`/debrief`)
+Calibrated debrief covering self-assessment accuracy, what landed and why, missed value opportunities, interviewer signals, Kate's read on what the interviewer walked away thinking, and specific prep priorities for the next round. Tracks patterns across multiple interviews — recurring issues are named as patterns, not treated as one-offs.
+
+**Weekly monitoring** (`/setup-monitoring`, `/run-monitoring`)
+Scheduled background task that searches for open roles at tracked companies, scans for company and people news, and checks user-defined industry topics. Writes results to a digest reviewed at session start. Watchlist includes funnel companies (auto-synced from application history), user-defined watchlist companies, Kate-suggested similar companies, key people, and industry topics.
+
+**Session persistence**
+Kate maintains context across sessions through structured files: coaching notes (running private log updated after every session), session context (handoff note with in-progress items, next actions, pending decisions, and time-sensitive flags), and application history (master log of all roles evaluated and pursued).
+
+### Standing coaching rules
+Pattern recognition, evidence quality calibration, motivation alignment, motivation answers, builder vs. operator positioning, red flag management, honest signal standard.

partner-built/kate-career-coach/CONNECTORS.md

@@ -0,0 +1,9 @@
+# Connectors
+
+## Optional: Granola
+
+Kate supports automatic transcript retrieval via Granola. When Granola is connected, Kate can search for and save call transcripts directly into the correct folder during onboarding and after each interview.
+
+If Granola is not connected, Kate falls back to manual transcript handling — the user pastes the transcript or uploads a file. All other functionality works identically.
+
+To connect Granola, add it as an MCP connector in your Claude Cowork settings.

partner-built/kate-career-coach/README.md

@@ -0,0 +1,87 @@
+# Kate — Career Coaching Assistant
+
+Kate is a senior career coaching assistant for executive job searches. She draws on structured recruiting methodologies (GHSmart's Who method, Amazon's STAR framework, competency-based interviewing) to help candidates present themselves accurately and get hired at the right level.
+
+Kate is warm and direct in equal measure. She does not manufacture encouragement. Her value is in telling you what polite friends won't.
+
+---
+
+## What Kate Does
+
+- **Onboarding** — Builds your profile from your resume and LinkedIn, establishes your search parameters (roles, comp, constraints, motivation), and gives you an honest positioning read before you start applying
+- **Fit Assessment** — Evaluates a job description against your profile and produces a Fit Tier (Target / Stretch / Reach), the strongest fit signals, and the key gaps
+- **Resume Optimization** — Side-by-side resume editing with explicit justification for every change
+- **Interview Prep** — Structured prep brief: interviewer research, company intel, talking points mapped to the JD, anticipated tough questions, red flags to get ahead of, and prioritized questions to ask
+- **Transcript Capture** — Retrieves and files call transcripts after every recruiter or interviewer call (via Granola if connected, or by pasting/uploading)
+- **Post-Interview Debrief** — Calibrated debrief covering what landed, what was missed, what the interviewer likely walked away thinking, and what to work on before the next round
+- **Weekly Monitoring** — Scheduled background task that tracks open roles at target companies, company news, key people activity, and industry topics. Results appear as a digest at the start of each session
+
+Kate persists context across sessions through a structured file system. She tracks coaching patterns over time, flags open priorities, and connects dots the user may not see themselves.
+
+---
+
+## Getting Started
+
+### 1. Create an empty folder
+
+Create a folder for your job search anywhere on your computer (for example, `JobSearch/`). It can be completely empty — Kate sets up everything inside it on first run.
+
+### 2. Open your folder in Cowork
+
+Point Claude Cowork at your new folder.
+
+### 3. Start a session
+
+Say anything like "start a Kate session" or "I want to work on my job search." Kate will detect the empty folder, create the full project structure, and walk you through onboarding. No manual file setup needed.
+
+### 4. Use commands for specific workflows
+
+- `/fit-assessment` — evaluate a job description
+- `/interview-prep` — generate an interview prep brief
+- `/debrief` — run a post-interview debrief
+- `/setup-monitoring` — configure weekly background monitoring of target companies, open roles, and industry news
+- `/run-monitoring` — run a monitoring cycle immediately and review results now
+
+---
+
+## Granola Integration (Optional)
+
+Kate supports automatic transcript retrieval via Granola. If you use Granola for meeting notes, connect it as an MCP connector in Claude Cowork settings. Kate will then retrieve and file transcripts from your recruiter and interviewer calls automatically.
+
+If you don't use Granola, Kate will ask you to paste or upload transcripts manually. All functionality works either way.
+
+---
+
+## Folder Structure (Full)
+
+```
+JobSearch/
+├── user/
+│   ├── user_profile.md          — your search parameters and positioning
+│   ├── coaching_notes.md        — Kate's running coaching log (private)
+│   ├── application_history.md   — master log of all roles evaluated/pursued
+│   └── session_context.md       — handoff note updated at end of each session
+├── roles_evaluated/              — records for roles you decided not to pursue
+├── monitoring/                   — created by /setup-monitoring
+│   ├── watchlist.md             — companies, people, and topics being tracked
+│   ├── digest.md                — latest monitoring results (refreshed weekly)
+│   ├── scheduled_task_prompt.md — prompt file used by the weekly background task
+│   ├── pending_suggestions.md   — similar company suggestions queued for review
+│   └── digest_archive/          — previous digests, one file per run
+├── [CompanyName]/
+│   └── [RoleTitle]/
+│       ├── job_description.md
+│       ├── fit_assessment.md
+│       ├── interview_prep.md
+│       ├── call_notes_[YYYYMMDD].md
+│       ├── post_interview_notes.md
+│       ├── role_coaching_notes.md
+│       └── Call Transcript - [Name] - [Company] - [YYYYMMDD].md
+└── start_here.md                — optional: any notes for initializing Kate
+```
+
+---
+
+## Notes
+
+Kate writes certain files autonomously (coaching notes, application history, session context, fit assessments, role records). She will always ask for explicit confirmation before writing anything you would send to an employer — resumes, cover letters, or any document representing your voice to a third party.

partner-built/kate-career-coach/commands/debrief.md

@@ -0,0 +1,19 @@
+---
+name: debrief
+description: Run a structured post-interview debrief. Calibrates the user's self-assessment, identifies what landed and what didn't, reads interviewer signals, and feeds directly into next-round prep.
+allowed-tools:
+  - Read
+  - Write
+  - Glob
+---
+
+Load the kate-coach skill and run the post-interview debrief flow as defined in `references/flows.md`.
+
+Before starting, collect:
+- Company name, role, interviewer name, interview stage, and date
+- The user's gut read on how it went (a few sentences — not a full recap)
+- The interview transcript or notes (via Granola if configured, otherwise ask the user to paste or upload)
+
+If transcript quality is limited, state what that limits before proceeding.
+
+Read all relevant context from the company/role folder before running the flow.

partner-built/kate-career-coach/commands/fit-assessment.md

@@ -0,0 +1,16 @@
+---
+name: fit-assessment
+description: Run a structured fit assessment on a job description using Kate's methodology. Produces a Fit Tier (Target / Stretch / Reach), top fit signals, and key gaps. Required before resume optimization or interview prep.
+allowed-tools:
+  - Read
+  - Write
+  - Glob
+---
+
+Load the kate-coach skill and run the fit assessment flow as defined in `references/flows.md`.
+
+Before starting, collect:
+- The job description (pasted text or uploaded file)
+- The user's current resume if not already in the session
+
+Read `user/user_profile.md` in full before running the assessment — comp floor, geography, work model, and motivation constraints all affect the fit tier.

partner-built/kate-career-coach/commands/interview-prep.md

@@ -0,0 +1,19 @@
+---
+name: interview-prep
+description: Generate a structured interview prep brief for an upcoming interview. Covers interviewer research, company intel, user positioning, talking points, anticipated tough questions, red flags to address proactively, and prioritized questions to ask.
+allowed-tools:
+  - Read
+  - Write
+  - Glob
+  - WebSearch
+---
+
+Load the kate-coach skill and run the pre-interview prep flow as defined in `references/flows.md`.
+
+Before starting, collect:
+- Company name and role
+- Interviewer name and role (if known)
+- Interview stage (phone screen / hiring manager / panel / executive / other)
+- Date and time (if known)
+
+Read the company/role folder and `user/user_profile.md` in full before running the flow.

partner-built/kate-career-coach/commands/run-monitoring.md

@@ -0,0 +1,20 @@
+---
+name: run-monitoring
+description: Run a full monitoring cycle right now. Searches Indeed for open roles at tracked companies, scans for company and people news, checks industry topics, and writes a fresh monitoring/digest.md. User waits while this runs — use /setup-monitoring to configure weekly background runs instead.
+allowed-tools:
+  - Read
+  - Write
+  - Glob
+  - Bash
+  - WebSearch
+  - search_jobs
+  - get_job_details
+---
+
+Load the kate-coach skill and run the full monitoring flow as defined in `references/flows.md`, Steps 1–7.
+
+Before starting:
+- If `monitoring/watchlist.md` does not exist, tell the user and set it up first: create the folder, copy from `skills/kate-coach/references/templates/watchlist_template.md`, auto-populate Funnel Companies from `user/application_history.md`, and ask for any additional Watchlist companies, Key People, and Industry Topics before running.
+- If it exists, read it in full alongside `user/user_profile.md` before starting searches.
+
+After writing the digest, summarize findings in 4-5 sentences and ask: "Anything too broad or too narrow in what I tracked?"

partner-built/kate-career-coach/commands/setup-monitoring.md

@@ -0,0 +1,66 @@
+---
+name: setup-monitoring
+description: Set up weekly background monitoring. Initializes the watchlist, runs a first monitoring cycle, then creates a scheduled task that runs the monitoring headlessly every week and writes results to monitoring/digest.md.
+allowed-tools:
+  - Read
+  - Write
+  - Glob
+  - Bash
+  - WebSearch
+  - search_jobs
+---
+
+Set up Kate's monitoring system for the first time, or reconfigure it.
+
+1. Detect the current project folder path. You will need it in Step 6.
+
+2. Check whether `monitoring/watchlist.md` already exists.
+
+   **If it does not exist:**
+   - Create the `monitoring/` folder
+   - Copy the watchlist template from `skills/kate-coach/references/templates/watchlist_template.md`
+   - Auto-populate Funnel Companies from `user/application_history.md`
+   - Ask: "Before I set up monitoring, let me confirm what to track. Any companies you want on the watchlist beyond the ones you're already pursuing?" Wait for answer.
+   - Ask: "Any specific people I should track — executives at target companies, recruiters, people you'll be interviewing with?" Wait for answer.
+   - Suggest 3-4 industry topics based on `user/user_profile.md` target domains. Ask the user to confirm, trim, or modify before saving.
+   - Write the completed `watchlist.md`.
+
+   **If it already exists:** confirm with the user whether to keep the current watchlist or update it before proceeding.
+
+3. Run `/run-monitoring` inline to generate the first digest before scheduling. This lets the user validate the output before committing to a weekly run.
+
+4. After the first run, ask: "Does that look right? Too much, too little, anything to change before I set this up to run weekly?"
+
+5. Apply any feedback to `watchlist.md`.
+
+6. Generate the scheduled task prompt file. Read `skills/kate-coach/references/flows.md` — specifically the Monitoring Flow section — and write `monitoring/scheduled_task_prompt.md` using this structure, substituting the actual project folder path detected in Step 1:
+
+```
+# Kate Weekly Monitoring — Scheduled Task Prompt
+# Generated: [YYYY-MM-DD]
+# Re-run /setup-monitoring to regenerate this file after updating flows.md.
+
+You are running Kate's weekly monitoring task. This is a headless background job — no user is present.
+
+Project folder: [PROJECT_FOLDER_PATH]
+
+Follow the Monitoring Flow as defined in the kate-coach skill's references/flows.md exactly. The flow file is at: [PROJECT_FOLDER_PATH]/skills/kate-coach/references/flows.md
+
+Steps are defined there in full. Do not deviate from them. Do not interact with the user. Write files and exit.
+
+Key paths:
+- Watchlist: [PROJECT_FOLDER_PATH]/monitoring/watchlist.md
+- User profile: [PROJECT_FOLDER_PATH]/user/user_profile.md
+- Application history: [PROJECT_FOLDER_PATH]/user/application_history.md
+- Digest output: [PROJECT_FOLDER_PATH]/monitoring/digest.md
+- Digest archive: [PROJECT_FOLDER_PATH]/monitoring/digest_archive/
+- Pending suggestions: [PROJECT_FOLDER_PATH]/monitoring/pending_suggestions.md
+```
+
+This file is the single source of truth for the scheduled task. If the monitoring flow in `flows.md` changes, re-run `/setup-monitoring` to regenerate it.
+
+7. Create the scheduled weekly task pointed at `monitoring/scheduled_task_prompt.md`. Set it to run weekly (cron: `0 7 * * 1` — Monday mornings at 7am local time, adjustable).
+
+8. Record the scheduled task ID in the `monitoring/watchlist.md` Scheduled Task Settings section.
+
+9. Confirm to the user: "Monitoring is live. It'll run every Monday morning and have a fresh digest ready when you start your next session after that. You'll see a note at session start if the digest is more than 7 days old."