Use this skill when the user says "I have an interview", "help me prepare", "prep for my interview at {company}", "create interview prep", or "company overview". Also handles the `/jfm:prep` command and triggers when a role moves to the interviewing stage. Generates two research documents: a company overview and an interview prep guide with experience-mapped case studies.
Create research documents that help the user walk into an interview with company context and pre-mapped case studies.
interviewing stageRead profile.yaml and tracker.yaml
Find the application matching the company name:
node ${CLAUDE_PLUGIN_ROOT}/scripts/tracker.js find --company "Company Name"
If multiple roles are returned for the same company, list them with role titles and stages and ask which one:
I found two roles at Google:
Which one are you prepping for?
Get file paths for the chosen application:
node ${CLAUDE_PLUGIN_ROOT}/scripts/tracker.js paths --id <id>
This returns company_dir, role_dir, and current file locations.
If a JD exists (check has_jd from paths output), read it. If not, ask the user for the job posting URL and fetch it.
Read the user's evidence: fetch resume URL if provided, read portfolio URLs, read additional context.
Generate the two documents below.
Save files to the company structure:
{company_dir}/overview.md (shared across roles at this company){role_dir}/prep.md (role-specific)
Create directories with mkdir -p if they don't exist.Update the application's stage to interviewing in tracker.yaml if it isn't already.
Show the user what was created. After saving, present the documents inline:
Company Overview —
{company_dir}/overview.md{Show a 3-4 line summary of what the overview covers}Interview Prep —
{role_dir}/prep.md{Show a 3-4 line summary: number of topics covered, key areas, questions to ask}Read the full docs in
{company_dir}/or click the links on your board.
Use present_files to share the created files and Kanban/index.html with the user.
If no company name is provided, check the tracker for roles in any non-terminal stage and list them, prioritizing interviewing and applied:
Which role are you prepping for?
Interviewing:
- Acme Corp — VP Engineering
Applied:
- BigCo — Director of Programs
Other active roles:
- Google — Staff Engineer (maybe)
- Google — Engineering Manager (suggested)
Or paste a job posting URL and I'll prep for that one.
This makes it easy to pick without remembering exact names. Always show the role title — company name alone is ambiguous when there are multiple roles at the same company.
You MUST create exactly TWO separate files. Do not combine them. They serve different purposes and appear as separate links on the board.
{company_dir}/overview.mdThis is a company-level document shared across all roles at this company. If it already exists, skip it.
Research the company and write a concise overview covering:
Keep it scannable — 10 minutes to read before an interview. This file contains ONLY company research. No interview questions, no experience mapping.
{role_dir}/prep.mdThis is a role-specific document. It contains everything the user needs to prepare for interviews for THIS specific role.
Read references/prep-template.md for the detailed structure. The prep doc has three sections:
Section A — JD-Based Interview Topics
For each likely interview topic (inferred from the JD requirements):
profile.yaml evidence, resume, portfolio)Section B — Industry & Company Context Questions
Beyond the JD requirements, anticipate questions based on the company's industry, stage, and recent context. These are questions interviewers ask because of who they are, not just what the role needs.
Research the company to identify:
Generate 3-5 industry/context questions in the prep doc:
## Industry & Company Context Questions
### {Topic — e.g., "Regulated environment"}
**Why they'll ask**: {e.g., "Fintech companies always probe for compliance comfort"}
**Likely question**: "{e.g., Tell me about shipping in a regulated environment}"
**Your story**: {mapped from user's evidence}
Common patterns to check:
Generate 3-5 of these industry/context questions per company. They should feel like the questions a well-prepared candidate would expect but a generic prep guide would miss.
Section C — Questions to Ask Them
End the prep doc with 5-8 thoughtful questions that demonstrate research and genuine curiosity about the role. These should be specific to the company and role, not generic.
Reminder: File 1 (overview.md) = company research only. File 2 (prep.md) = Sections A + B + C above. Two separate files, two separate links on the board.
Read the user's evidence in this order of preference:
profile.yaml → evidence.resume_url (fetch and read)profile.yaml → evidence.portfolio_urls (check for relevant projects)profile.yaml → evidence.additional_context (user-written narrative)archetypes.yaml → the matched role type's experience_mappingThe user's thinnest area is typically case studies — the interview prep doc should do the heavy lifting of connecting their experience to the role's requirements. Don't just list qualifications; tell the user which story to tell for each topic.
Company overview research uses Sonnet sub-agents. Interview prep generation uses the main Opus agent for deeper reasoning about experience mapping.
references/prep-template.md — full template with section structure and examples