name: interview-prep
description: Prepare for an upcoming interview by researching the company, pulling relevant stories, and matching experience to role requirements. Use when user says "prep for [company]", "interview prep", or has an interview scheduled.

Interview Prep

Prepare for an upcoming interview by researching the company, pulling relevant stories, and matching experience to role requirements.

Trigger

Use when:
- Terry has an interview scheduled
- User says "prep for [company]", "interview prep", "prepare for interview"

Inputs

• company: Company name (required)
• role: Role title (required)
• stage (optional): Phone screen, hiring manager, technical, etc.
• date (optional): Interview date/time

Workflow

1. Read context files:
2. /Users/terry/notes/CLAUDE.md — personal context
3. /Users/terry/notes/Core Story Bank.md — prepared stories (if exists)
4. /Users/terry/notes/Interview Preparation.md — general prep notes (if exists)

5. /Users/terry/notes/Job Hunting.md — notes on this role/company

6. Research interviewer (if name known):

7. /counter-intel — Research interviewer background and style

8. Search vault for past interactions with this person

9. Research company via web search:

10. Recent news — last 3-6 months, anything notable
11. Tech stack — especially data/ML infrastructure
12. Culture signals — values, work style, reviews
13. Key people — who Terry might meet, their background

14. Challenges — problems they're likely solving

15. Get fresh AI news (for AI-forward companies):

16. Run /ai-news quick for recent developments and talking points
17. Especially useful if interview is >1 week away

18. Shows awareness of industry trends

19. Map role to experience:
    | Role Requirement | Terry's Relevant Experience |
    |------------------|----------------------------|
    | [Requirement] | [Matching experience/story] |

20. Select 3-5 stories from Core Story Bank most relevant to this role

21. Cross-check with narrative debt log to avoid repetition

22. Prioritize stories NOT yet told to this company

23. Generate 5-7 questions to ask (tailored to research findings):

24. Role-specific (day-to-day, expectations, success metrics)
25. Team/culture (how team works, collaboration)

26. Company direction (strategy, challenges, growth)

27. Flag potential concerns:

28. Gaps or transitions to address
29. Why leaving current role (clean narrative)
30. Salary expectations if likely to come up

31. Red flags from research

32. Review with Judge:

33. Run prep output through /judge with technical criteria
34. Check: completeness, appropriate_depth, actionable
35. If verdict is needs_work: revise (max 2 iterations)

36. Ensures prep is comprehensive and interview-ready

37. Save prep notes to vault (optional)

Related Skills

• /counter-intel — Interviewer research and profile building
• /debrief — Capture signals after the interview
• /ai-news — Fresh AI news for talking points
• vault-pathfinding — Vault paths for reading context files

Error Handling

• If Core Story Bank doesn't exist: Note what stories Terry should prepare
• If company info sparse: Focus on role requirements and general prep
• If interview is soon: Focus on essentials; if days away, go deeper

Output

Template:

# Interview Prep: [Company] - [Role]

## Company Briefing
[Concise summary — recent news, tech stack, culture]

## Role Mapping
| Requirement | Your Experience |
|-------------|-----------------|

## Stories to Use
1. [Story name] — [why relevant]

## Questions to Ask
1. [Question]

## Watch Out For
- [Concern and how to address]

## Next Steps
- [Any prep actions before interview]

Location: /Users/terry/notes/Interview Prep - [Company].md

Examples

User: "prep for Stripe"
Action: Research Stripe, map experience, select stories, generate questions
Output: Interview prep note saved to vault, summary in chat