cs-prep

Synthesize customer meeting history into structured Markdown QBR briefs.

1|2|Updated Dec 3, 2025
One-click install
npx skills add https://github.com/jayhjenkins/ProductOSv0.2 --skill cs-prep
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cs-prep
Source: https://github.com/jayhjenkins/ProductOSv0.2/tree/main/.claude/skills/workflows/cs-prep
Command: npx skills add https://github.com/jayhjenkins/ProductOSv0.2 --skill cs-prep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill compiles customer-specific meeting history, extracts signals, quotes, and pain points, and timelining feature requests to prepare for QBRs and strategic CS discussions.

Core Features & Use Cases

  • Customer-specific history synthesis: Aggregate meetings and interactions to build a coherent narrative.
  • Signal and quote extraction: Identify wins, pain points, onboarding friction, and feature requests with attributions.
  • Timeline generation: Create a chronological log of requests and events for roadmaps and discussions.
  • CS Brief generation: Produce a structured brief file suitable for distribution and review.

Quick Start

Use the cs-prep skill to generate a QBR brief by specifying the customer name and a lookback window, for example: cs-prep --customer AcmeCorp --days 90

Frequently Asked Questions about cs-prep

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I synthesize customer meeting history into a structured QBR brief?▼

This Skill synthesizes customer meeting history into a structured QBR brief by extracting signals, quotes, and pain points across a specified lookback window. It outputs a Markdown file aggregating wins and timelines for strategic customer success reviews.

How do I create a timeline of feature requests from customer interactions for a QBR?▼

You can create a timeline of feature requests by specifying a customer name and lookback window. The Skill chronologically logs requests and events from your meeting history to build a coherent narrative for roadmaps and discussions.

What inputs do I need to generate a customer success brief?▼

You need the customer name and a lookback window in days to generate a customer success brief. The Skill processes these inputs to extract signals and output a Markdown file at datasets/product/customer-briefs/{Customer}_{YYYYMMDD}_qbr.md.

Can I extract pain points and quotes from past meetings for customer reviews?▼

Yes, you can extract pain points and quotes from past meetings for customer reviews. The Skill identifies wins, onboarding friction, and feature requests with attributions by leveraging meeting-synthesis for signal extraction across a specified lookback window.

Does the QBR brief generation process work without a meeting-synthesis component?▼

No, QBR brief generation explicitly leverages the meeting-synthesis skill for signal extraction. It relies on this underlying process to identify wins, pain points, and onboarding friction from raw customer interaction history before compiling the final Markdown brief.