Interview Prep Kit

Produces a durable written artifact, not a live roleplay — use mock-interview for the interactive practice; this skill builds the reference doc that feeds it.

Inputs

• Resume: a file path the user provides, or pasted text. If neither is given, ask for one — don't fabricate work history. Never send resume content anywhere outside this project; it's processed locally into the kit doc only.
• Job posting: a URL (fetch it) or pasted text. If a topics/interview-prep/<company-slug>/ or TRAINING.md company row already has notes, use them as background, but re-derive requirements from the actual posting, not memory.

Building the kit

Write to topics/interview-prep/<company-role-slug>-prep-kit.md:

1. One-page summary (top of the doc) — role, company, the 3-4 things this interview loop will most likely probe, and the candidate's single strongest angle for this specific role. This is the part to skim right before the interview.
2. Requirement-by-requirement mapping — take each requirement/responsibility from the posting and map it to specific resume evidence (a project, a metric, a line item). Where there's a genuine gap (skill/experience not on the resume), say so plainly and suggest how to address it honestly in conversation (a related transferable experience, or "I'd frame this as...") rather than inventing experience or hiding the gap.
3. STAR story bank — 4-8 stories pulled from the resume, each with Situation/Task/Action/ Result filled in from what the user actually did (ask follow-up questions to fill gaps, don't guess at outcomes/metrics). Tag each story with the competencies/values it demonstrates (e.g. Amazon Leadership Principles, or the role's stated qualities) so it's easy to pick the right story live in mock-interview.
4. Company/domain fluency cheat sheet — product lineup, recent moves relevant to the role, likely technical stack, and anything from TRAINING.md's company-prep or platform-basics rows worth citing. Flag anything time-sensitive (funding, recent launches) as something to verify is still current closer to the actual interview.
5. Questions to ask — 4-6 real questions calibrated to this role/company, split between "shows genuine technical curiosity" and "surfaces something the candidate actually needs to know to evaluate the offer."

After building

• Note the kit's path in TRAINING.md's "Company / role prep" row for this company (add one if missing).
• Suggest running mock-interview next using the story bank and gap list as live material, rather than starting a mock round cold.
• If the kit surfaces a real skill gap, suggest a matching train-topic session to close it before the interview, don't just note it and move on.