tjboudreaux/cc-plugin-product-strategist · Archived

product-behavior-signals

Convert mixed-method research and live telemetry into actionable user insight loops that guide product bets.

First seen May 20, 2026

Installation

$ npx skills add tjboudreaux/cc-plugin-product-strategist --skill product-behavior-signals

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from tjboudreaux/cc-plugin-product-strategist.

npx skills add tjboudreaux/cc-plugin-product-strategist

Browse all from tjboudreaux/cc-plugin-product-strategist

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 2
License LICENSE
Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,525 B
  • docs SUMMARY.md 140 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 7 installs

SKILL.md

Behavior Signal Intelligence

Intent

  • Triangulate qualitative stories with quantitative funnels to uncover true motivation, anxiety, and habit loops.
  • Maintain a living evidence stack that de-risks product, game, or web3 bets.

Required Inputs

  1. Latest analytics dashboards or raw event exports.
  2. Recent interview/UGC transcripts, community threads, customer support logs.
  3. Current instrumentation coverage map (events, properties, cohorts).

Workflow

  1. Instrument gap check

- Audit current telemetry vs. critical behaviors; file gaps immediately.

  1. Pattern mining

- Cluster behaviors by intent (explorers, creators, whales, lurkers, churned) using both quant cuts and qual quotes. - Map anxieties vs. triggers vs. rewards.

  1. Insight synthesis

- For each cluster, craft a “belief statement” (user tension + evidence + implication). - Link to supporting artifacts (charts, clips, tickets).

  1. Action routing

- Translate belief statements into testable hypotheses or backlog items with owners. - Set review cadence (weekly insight review, monthly deep dive).

Verification

  • Every belief statement references at least one quantitative and one qualitative source.
  • Instrumentation gaps tracked with owners/dates.
  • Insight backlog reviewed with product/game leads and updated within the last sprint.