competitive-intelligence-agent-oss

analyzes customer feedback across Email, GitHub, NPS, and churn cancellations.

Analyzes git history from a repository to summarize recent development activity, features in progress, and engineering priorities. Use when asked about what the team is working on, recent code changes, development velocity, or to prepare for planning/roadmap discussions.

Projects a customer's cost from prior usage data across seat-based, usage-based, and hybrid SaaS pricing models. Use when asked to "project cost", "estimate BYO cost", "estimate spend", "how much will this cost", "size a deal", or to build an enterprise-style usage/cost projection.

Does research on competitive features and creates a report.

Reads the most recent weekly product briefing, identifies P0 issues, researches them in the codebase, and spawns cloud coding agents to fix each one. Use when asked to "fix P0s", "address critical issues", or "work on top priorities from the briefing."

Posts messages to Slack via webhook.

Reads content from a specific Google Doc by URL or document ID.

Does research on competitor's changelogs.

Reads internal documents and creates a summary.

Extracts customer insights from Grain meeting transcripts across all feedback channels over the last 7 days. Analyzes pain points, feature demand, and competitive signals from external customer meetings. Use when asked for "voice of the customer", "VoTC analysis", "customer call insights", or "what are customers saying."

Weekly sentiment summary of your product's social mentions with week-over-week comparison using Octolens. Produces a markdown report with sentiment score, highlights, lowlights, notable patterns, and competitor context. Use when the user asks for a weekly sentiment report, weekly social summary, or "how did mentions look this week".

Compiles the most recent reports into a weekly What You Need to Know (WYNK) Notion page with sections for Executive Summary, Customer Feedback, Engineering Investments, Competitive Landscape, and Recommendations. Use when asked to "create a WYNK", "compile weekly reports", or "what do I need to know this week."

Skill for writing arbitrary Google Docs

Skill for interacting with Notion workspaces through the Notion REST API.

Writes Product Requirement Documents (PRDs) by synthesizing customer feedback, competitive research, git history, and internal docs into a structured, decision-ready spec. Use when asked to "write a PRD", "create a product spec", "draft requirements for [feature]", "spec out [feature]", or "write a product requirements document."