Menü
Add or update a competitor profile, signals, and ICP insights in data/competitors/
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Create or edit corkboard-style investigation boards that visualize relationship networks between companies, people, and products. Use when the user wants to map out connections, create relationship diagrams, or build visual investigation boards.
Manage company/product logo images in media/. Auto-fetch missing logos from logo.dev API.
Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD.
Convert PRDs to prd.json format for the Ralph autonomous agent system. Use when you have an existing PRD and need to convert it to Ralph's JSON format.
| name | competitor-intel |
| description | Add or update a competitor profile, signals, and ICP insights in data/competitors/ |
| user_invocable | true |
| triggers | ["/competitor-intel"] |
User provides a competitor name and any raw context (URL, news, notes). If no context given, ask.
Profile - Create or update data/competitors/<slug>/profile.yaml:
name: Acme Corp
category: direct | adjacent | emerging
positioning: <one-line how they position themselves>
overlap: 1-5 # market overlap with us
color: coral | gold | blue | violet | emerald
Derive positioning from how the competitor describes themselves publicly - not our opinion of them.
Signals - Add entries to data/competitors/signals/<YYYY-MM>-H<1|2>.yaml (H1 = days 1-15, H2 = days 16+). Create file if missing.
signals:
- competitor: <slug>
type: product | pricing | content | hiring | partnerships | funding
date: YYYY-MM-DD
description: >
What happened, factually.
action: opportunity | watch | respond
insight: >
What this means for us specifically.
Every signal must have an insight - connect it to our GTM position.
ICP & Insights - Review data/competitors/icp/segments.yaml and insights.yaml. If this competitor changes the landscape:
insights.yaml if a new cross-competitor pattern emergesDon't add insights that duplicate existing ones - update them instead.
Validate - Run cd dashboard && bun run vite build to confirm YAML loads correctly.