case-study-prep

name	case-study-prep
platforms	["cowork"]
description	Create Tiger Data case study interview prep documents. Gathers customer information via DM to the @eon Slack bot and user-provided Google Docs, then aligns all known information against the 8 standard Tiger Data Case Study Questions, producing a .docx with status ratings (Complete/Partial/Missing), draft answers, gap analysis, a 30-minute interview guide, and draft pull quotes. MANDATORY TRIGGERS: case study, interview prep, case study prep, customer story, customer interview, case study questions, ClickHouse takeout, competitive win story. Use when the user asks to prepare for a customer case study interview, create a case study prep doc, or align existing customer notes against the Tiger Data case study questions template.
references	["case-study-questions","case-study-output-format"]

Case Study Interview Prep

Produce a .docx case study prep document for a given customer by gathering all available information and aligning it to the 8 Tiger Data Case Study Questions.

Step 0: Pre-flight check

Invoke the marketing-preflight skill via the Skill tool, passing this skill's name: field value (case-study-prep) as the args. Do not proceed until it completes successfully. If it stops with an error, follow its instructions and stop.

If marketing-preflight returned a stale-connector footer note, append it verbatim at the end of your final response to the user.

Also fetch the No Fly List before doing any work:

get_marketing_reference(slug: "no-fly-list")

This is a list of customers who cannot be publicly referenced. If the customer you are preparing a case study for appears on the No Fly List, stop immediately and inform the user that this customer cannot be publicly referenced. If a No Fly List name appears in source material you are working from, omit it from all outputs.

Workflow

Step 1: Identify inputs

Determine from the user:

• Customer name (required)
• Context documents (optional): Google Doc URLs, uploaded files, or other sources containing existing customer notes
• If no context docs are provided, ask the user

Step 2: Gather information from Slack via Eon

Read CONFIG.md from the plugin root to get the current eon bot user ID.

1. Send a DM to eon (use the bot's user ID from CONFIG.md as the channel_id): Summarize current use case and metrics for customer {Company Name}
2. Capture the message_ts and channel_id from the send response
3. Wait ~30 seconds, then read the thread using the returned channel_id and message_ts to capture eon's response
4. If eon's response is incomplete or the thread hasn't been answered yet, wait and retry

Step 3: Fetch context documents

Fetch all user-provided Google Docs using google_drive_fetch. Also read any uploaded files.

Step 4: Fetch reference docs from Tiger Den

Before generating the document, fetch the two reference docs from Tiger Den:

get_marketing_context(slugs: ["case-study-questions", "case-study-output-format"])

• case-study-questions — the 8 standard Tiger Data Case Study Questions
• case-study-output-format — document structure and styling for the prep doc

If Tiger Den is not connected, do not proceed — tell the user to run /setup. See REFERENCES.md in the plugin root for details and error handling.

Also read the docx skill for .docx generation best practices (critical for correct docx-js usage).

Step 5: Compile and assess

For each of the 8 case study questions:

1. Synthesize all available information (eon response + context docs + any other sources)
2. Draft an answer using all known facts
3. Assign a status:
   • Complete: Enough detail to write a full answer with no major gaps
   • Partial: Directional answer exists but specific details, metrics, or quotes are missing
   • Missing: No meaningful information available
4. Identify specific gaps to close during the interview

Step 6: Generate the .docx

Create a Word document using docx-js following the structure in case-study-output-format:

• Title + subtitle
• Status legend table
• 8 question sections with status/details tables
• 30-minute interview guide (questions target ONLY the identified gaps)
• Draft pull quotes
• Sources list

Save to the outputs folder as {Company}_Case_Study_Prep.docx.

Validate with the docx skill's validate.py script.

Step 7: Present results

Share the document link and a quick summary showing each question's status at a glance.