pipeline-review
Analyze pipeline health — prioritize deals, flag risks, get a weekly action plan. Use when running a weekly pipeline review, deciding which deals to focus on this week, spotting stale or stuck opportunities, auditing for hygiene issues like bad close dates, or identifying single-threaded deals.
What this skill does
# /pipeline-review > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). Analyze your pipeline health, prioritize deals, and get actionable recommendations for where to focus. ## Usage ``` /pipeline-review [segment or rep] ``` Review pipeline for: $ARGUMENTS If a file is referenced: @$1 --- ## How It Works ``` ┌─────────────────────────────────────────────────────────────────┐ │ PIPELINE REVIEW │ ├─────────────────────────────────────────────────────────────────┤ │ STANDALONE (always works) │ │ ✓ Upload CSV export from your CRM │ │ ✓ Or paste/describe your deals │ │ ✓ Health check: flag stale, stuck, and at-risk deals │ │ ✓ Prioritization: rank deals by impact and closability │ │ ✓ Hygiene audit: missing data, bad close dates, single-thread │ │ ✓ Weekly action plan: what to focus on │ ├─────────────────────────────────────────────────────────────────┤ │ SUPERCHARGED (when you connect your tools) │ │ + CRM: Pull pipeline automatically, update records │ │ + Activity data for engagement scoring │ │ + Historical patterns for risk prediction │ │ + Calendar: See upcoming meetings per deal │ └─────────────────────────────────────────────────────────────────┘ ``` --- ## What I Need From You **Option A: Upload a CSV** Export your pipeline from your CRM (e.g. Salesforce, HubSpot). Helpful fields: - Deal/Opportunity name - Account name - Amount - Stage - Close date - Created date - Last activity date - Owner (if reviewing a team) - Primary contact **Option B: Paste your deals** ``` Acme Corp - $50K - Negotiation - closes Jan 31 - last activity Jan 20 TechStart - $25K - Demo scheduled - closes Feb 15 - no activity in 3 weeks BigCo - $100K - Discovery - closes Mar 30 - created last week ``` **Option C: Describe your pipeline** "I have 12 deals. Two big ones in negotiation that I'm confident about. Three stuck in discovery for over a month. The rest are mid-stage but I haven't talked to some of them in a while." --- ## Output ```markdown # Pipeline Review: [Date] **Data Source:** [CSV upload / Manual input / CRM] **Deals Analyzed:** [X] **Total Pipeline Value:** $[X] --- ## Pipeline Health Score: [X/100] | Dimension | Score | Issue | |-----------|-------|-------| | **Stage Progression** | [X]/25 | [X] deals stuck in same stage 30+ days | | **Activity Recency** | [X]/25 | [X] deals with no activity in 14+ days | | **Close Date Accuracy** | [X]/25 | [X] deals with close date in past | | **Contact Coverage** | [X]/25 | [X] deals single-threaded | --- ## Priority Actions This Week ### 1. [Highest Priority Deal] **Why:** [Reason — large, closing soon, at risk, etc.] **Action:** [Specific next step] **Impact:** $[X] if you close it ### 2. [Second Priority] **Why:** [Reason] **Action:** [Next step] ### 3. [Third Priority] **Why:** [Reason] **Action:** [Next step] --- ## Deal Prioritization Matrix ### Close This Week (Focus Time Here) | Deal | Amount | Stage | Close Date | Next Action | |------|--------|-------|------------|-------------| | [Deal] | $[X] | [Stage] | [Date] | [Action] | ### Close This Month (Keep Warm) | Deal | Amount | Stage | Close Date | Status | |------|--------|-------|------------|--------| | [Deal] | $[X] | [Stage] | [Date] | [Status] | ### Nurture (Check-in Periodically) | Deal | Amount | Stage | Close Date | Status | |------|--------|-------|------------|--------| | [Deal] | $[X] | [Stage] | [Date] | [Status] | --- ## Risk Flags ### Stale Deals (No Activity 14+ Days) | Deal | Amount | Last Activity | Days Silent | Recommendation | |------|--------|---------------|-------------|----------------| | [Deal] | $[X] | [Date] | [X] | [Re-engage / Downgrade / Remove] | ### Stuck Deals (Same Stage 30+ Days) | Deal | Amount | Stage | Days in Stage | Recommendation | |------|--------|-------|---------------|----------------| | [Deal] | $[X] | [Stage] | [X] | [Push / Multi-thread / Qualify out] | ### Past Close Date | Deal | Amount | Close Date | Days Overdue | Recommendation | |------|--------|------------|--------------|----------------| | [Deal] | $[X] | [Date] | [X] | [Update date / Push to next quarter / Close lost] | ### Single-Threaded (Only One Contact) | Deal | Amount | Contact | Risk | Recommendation | |------|--------|---------|------|----------------| | [Deal] | $[X] | [Name] | Champion leaves = deal dies | [Identify additional stakeholders] | --- ## Hygiene Issues | Issue | Count | Deals | Action | |-------|-------|-------|--------| | Missing close date | [X] | [List] | Add realistic close dates | | Missing amount | [X] | [List] | Estimate or qualify | | Missing next step | [X] | [List] | Define next action | | No primary contact | [X] | [List] | Assign contact | --- ## Pipeline Shape ### By Stage | Stage | # Deals | Value | % of Pipeline | |-------|---------|-------|---------------| | [Stage] | [X] | $[X] | [X]% | ### By Close Month | Month | # Deals | Value | |-------|---------|-------| | [Month] | [X] | $[X] | ### By Deal Size | Size | # Deals | Value | |------|---------|-------| | $100K+ | [X] | $[X] | | $50K-100K | [X] | $[X] | | $25K-50K | [X] | $[X] | | <$25K | [X] | $[X] | --- ## Recommendations ### This Week 1. [ ] [Specific action for priority deal 1] 2. [ ] [Action for at-risk deal] 3. [ ] [Hygiene task] ### This Month 1. [ ] [Strategic action] 2. [ ] [Pipeline building if needed] --- ## Deals to Consider Removing These deals may be dead weight: | Deal | Amount | Reason | Recommendation | |------|--------|--------|----------------| | [Deal] | $[X] | [No activity 60+ days, no response] | Mark closed-lost | | [Deal] | $[X] | [Pushed 3+ times, no champion] | Qualify out | ``` --- ## Prioritization Framework I'll rank your deals using this framework: | Factor | Weight | What I Look For | |--------|--------|-----------------| | **Close Date** | 30% | Deals closing soonest get priority | | **Deal Size** | 25% | Bigger deals = more focus | | **Stage** | 20% | Later stage = more focus | | **Activity** | 15% | Active deals get prioritized | | **Risk** | 10% | Lower risk = safer bet | You can tell me to weight differently: "Focus on big deals over soon deals" or "I need quick wins, prioritize close dates." --- ## If CRM Connected - I'll pull your pipeline automatically - Update records with new close dates, stages, next steps - Create follow-up tasks - Track hygiene improvements over time --- ## Tips 1. **Review weekly** — Pipeline health decays fast. Weekly reviews catch issues early. 2. **Kill dead deals** — Stale opportunities inflate your pipeline and distort forecasts. Be ruthless. 3. **Multi-thread everything** — If one person goes dark, you need a backup contact. 4. **Close dates should mean something** — A close date is when you expect signature, not when you hope for one.
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.