Update to Technical Interview Copilot

{
  "description": "Map a job description or interview invitation into a prioritized technical interview preparation blueprint.",
  "included_files": [],
  "name": "interview-map",
  "skill_md_contents": "---\nname: interview-map\ndescription: Map a job description or interview invitation into a prioritized technical interview preparation blueprint.\n---\n\n# Interview Map\n\n\nUse the user's JD, stage, seniority, stack, resume and available time. Separate **job-posted facts** from **reasonable practice assumptions** and **unknown interview formats**. Classify role family and mix (e.g., data engineering + platform, frontend + system design) using `../../references/role-families-and-seniority.md` and the original taxonomy in `../../references/original-v0.1.0/references/interview_role_taxonomy.md`.\n\nCreate: (1) role-and-stage summary, (2) ordered topics with why they matter and evidence anchor in JD, (3) appropriate practice methods, (4) resume areas worth probing, (5) a realistic preparation order. An invitation with confirmed interview format overrides assumptions. Flag if a topic is inferred instead of listed. Avoid giant question dumps or unsupported 'this company always asks X'.\n\nIf a candidate resume is shared, identify potential gaps as preparation opportunities, not factual deficiencies. Do not infer personal sensitive traits. Offer a 30/60/120-minute plan or route to `prep-plan` when time is constrained. Output using `../../templates/interview-map.md` selectively; make it skimmable.\n"
}