fe-poc-postmortem

Generate post-mortem retrospectives from Google Docs, Salesforce, JIRA, and Slack sources.

Updated Feb 27, 2026
One-click install
npx skills add https://github.com/LaurentPRAT-DB/LPT_claude_config --skill fe-poc-postmortem
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fe-poc-postmortem
Source: https://github.com/LaurentPRAT-DB/LPT_claude_config/tree/main/skills/fe-vibe-export/fe-workflows/1.2.0/skills/fe-poc-postmortem
Command: npx skills add https://github.com/LaurentPRAT-DB/LPT_claude_config --skill fe-poc-postmortem

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This skill automates the creation of detailed post-mortem retrospective documents for competitive Proofs of Concept (POCs) that Databricks did not win, capturing crucial learnings to improve future engagements.

Core Features & Use Cases

  • Automated Data Gathering: Collects information from Salesforce, JIRA, Slack, Glean, and documents.
  • Narrative Synthesis: Generates a structured retrospective document with sections on summary, history, competition, challenges, and recommendations.
  • Use Case: After losing a competitive POC to Snowflake, use this skill with the opportunity ID and a link to the internal POC doc to automatically generate a comprehensive post-mortem, identifying key reasons for the loss and actionable recommendations for the sales and engineering teams.

Quick Start

Invoke the poc-postmortem agent with the user's request and available sources.

Frequently Asked Questions about fe-poc-postmortem

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

FAQPage Schema
How do I automate a postmortem for a lost competitive POC?

To automate a postmortem for a lost competitive POC, provide the Salesforce opportunity ID and internal document links to synthesize findings from JIRA, Slack, and Google Docs into a structured narrative retrospective with actionable recommendations.

What is a competitive POC retrospective and what should it include?

A competitive POC retrospective analyzes lost proof of concept engagements to identify learnings. It typically includes sections on opportunity history, competitive analysis, technical challenges, and actionable recommendations for future sales and engineering engagements.

Can I generate postmortem reports from Salesforce and JIRA data?

Yes, you can generate postmortem reports by parsing Salesforce opportunity records alongside JIRA tickets and Slack channels. The skill integrates these multiple data sources to synthesize a comprehensive narrative of the POC engagement.

How do I analyze lost Databricks POC engagements to improve sales enablement?

Analyze lost Databricks POC engagements by aggregating communication and technical data from various sources. This process identifies key reasons for losses and generates structured recommendations to improve future competitive sales enablement strategies.

What data sources are needed to create a comprehensive POC post-mortem?

Creating a comprehensive POC post-mortem requires data from Salesforce opportunities, JIRA tickets, Slack channels, Glean, and Google Docs. Parsing these multiple source types synthesizes findings into a narrative retrospective identifying key learnings.

Are there limitations to automating retrospective documents from Slack and Google Docs?

Automating retrospective documents from Slack and Google Docs depends on the accessibility and completeness of the conversation histories. The synthesized narrative quality is constrained by how thoroughly the POC challenges and history were documented in those platforms.