Merge Insights

Merge parallel extraction outputs into a unified insights JSON with Jira mapping.

14|2|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/rchandnaWUSTL/pm-digital-twin --skill merge-insights
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Merge Insights
Source: https://github.com/rchandnaWUSTL/pm-digital-twin/tree/main/skills/merge-insights
Command: npx skills add https://github.com/rchandnaWUSTL/pm-digital-twin --skill merge-insights

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill consolidates and structures data extracted from multiple sources, creating a unified view of customer insights without relying on LLM interpretation.

Core Features & Use Cases

  • Deterministic Merging: Combines outputs from various extraction skills (themes, asks, pain points, tool signals, Jira mapping) into a single JSON object.
  • Actionable Intelligence: Enriches extracted data with Jira issue mapping and recommends actions (update existing, create new).
  • Use Case: After running several extraction skills on customer call notes, use this Skill to automatically generate a comprehensive insights.json file that summarizes all key themes, customer asks, and their corresponding Jira ticket statuses.

Quick Start

Use the merge insights skill to combine all extraction outputs into a unified insights JSON file.

Frequently Asked Questions about Merge Insights

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

FAQPage Schema
How do I merge customer feedback from multiple sources into a single structured file?

To merge customer feedback, this Skill consolidates outputs from various parallel extraction tasks into a unified insights JSON file. It applies deterministic data merging rules to structure themes, asks, and pain points from unstructured call notes without relying on LLM interpretation.

What is deterministic data merging for unstructured call notes?

Deterministic data merging for unstructured call notes combines multiple extraction outputs into one JSON object using strict rules rather than LLM interpretation. This ensures reliable structuring of customer themes, product requests, and technical signals into a unified view.

Can I map extracted customer insights directly to Jira issues?

Yes, you can map extracted customer insights directly to Jira issues. The Skill enriches the unified JSON by mapping synthesized product requests and pain points to existing Jira tickets, recommending actions to update or create new issues for actionability.

Does Jira integration require any specific dependencies to synthesize product requests?

No specific dependencies are required for Jira integration to synthesize product requests. The Skill operates independently to map extracted technical signals and customer asks to existing Jira issues within its deterministic merging framework.

What's the best way to synthesize extraction outputs without LLM interpretation?

The best way to synthesize extraction outputs without LLM interpretation is using deterministic data merging rules. This approach reliably consolidates themes and tool signals from parallel extraction skills into a structured insights JSON file.

When should I use a deterministic merging approach over LLM synthesis for customer feedback?

You should use deterministic merging over LLM synthesis when you need reliable, repeatable structuring of customer feedback and technical signals. It is ideal when combining parallel extraction outputs into a unified insights JSON with strict Jira issue mapping.