Systems Lab

Agent skill

product-signal

Route post-sale and field signals into product's roadmap queue, and write the buyer-facing line for anything shipped.

activeSelf-containedInstructions only362 words

Filed under Prospecting and list building.

From etrebels/claude-code-growth-os · 20 skill entries · 21 · pushed 2026-10-03

What it does when it runs

Route post-sale and field signals into product's roadmap queue, and write the buyer-facing line for anything shipped. Trigger when the user says "what should product hear", "triage the roadmap signals", "route this to product", "feature request", or "what does this feature mean for the buyer".

Automated analysis of the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.

Keys and connectors you must supply
None found.
Hosts it reaches
No third-party host appears in the skill or its bundled files.
Tool permissions it declares
No allowed-tools in the frontmatter. It only issues instructions, so there is nothing to bound.
Actions present in the files
None. Instructions only.

Ask about product-signal

Opens your assistant with this page's verified links already in the prompt.

Is this safe to install?ClaudeChatGPT
Adapt it to my stackClaudeChatGPT
What else do I need for it to workClaudeChatGPT
Rather ask a human? Talk to Cheetah

Install it

View source on GitHub ↗
git clone --depth 1 --filter=blob:none --sparse https://github.com/etrebels/claude-code-growth-os.git /tmp/claude-code-growth-os
git -C /tmp/claude-code-growth-os sparse-checkout set ".claude/skills/product-signal"
mkdir -p ~/.claude/skills/product-signal
cp -R "/tmp/claude-code-growth-os/.claude/skills/product-signal/." ~/.claude/skills/product-signal/

Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗

The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.

The skill

Source on GitHub ↗

Reproduced in full from etrebels/claude-code-growth-os/blob/3e0c2d7d1fc545d35073011208d8da3f845183fb/.claude/skills/product-signal/SKILL.md, which is licensed MIT (repository). 362 words, 2 headings.

Product Signal

The product function's place in the loop. Marketing has marketing-feedback; CS has account-health; this is product's. It pulls the signals that should shape what gets built out of the shared log into product's own triage queue, and — for anything shipped — writes the one-line "what this means for the buyer" so a feature doesn't land silently. This closes handoffs H4 (CS→product) and H5 (product→GTM) in docs/operating-model.md.

From the shared feedback log (demo/feedback-log.md, or your own) and ops/customers.md:

  1. Pull the product-shaped signals. Three kinds belong on the roadmap, not in a meeting note:
    • RETENTION-RISK lines that are really a product gap — adoption friction or a missing capability, not a CS task.
    • FEATURE-REQUEST items that block an adoption or an expansion (the ones tied to a renewal or a second team).
    • Win/loss reasons that are about the product, not the deal — what we couldn't do that cost us, or won us, the deal.
  2. Route each into ops/roadmap-signals.md. One row per signal: the source, the type, the account or pattern it's tied to, where it's routed, and a status (New → Routed → Shipped). This is product's working surface — distinct from the raw log it's pulled from.
  3. Wait for the pattern on anything ambiguous. A single request isn't a roadmap item; a request that recurs across accounts, or one blocking a real renewal, is. Don't route noise.
  4. Close the loop on anything shipped. For each item that ships, write the one-line buyer-facing translation in the last column: what can the customer now do that they couldn't before — in their language, not the release note's. Hand that line to GTM (it's what marketing-feedback's readers and the deal follow-ups need). No feature ships without it — the antidote to building things no one adopts.

Don't promise a roadmap; this routes the signal and frames the outcome. The build decision is yours.

Depth

  • quick: pull the product-shaped signals from the log into ops/roadmap-signals.md.
  • standard: the full triage above — routed, status-tagged, patterns separated from noise.
  • deep: + the buyer-facing line for each shipped item, ready to hand to GTM.

Other skills for the same job

Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.

Need help setting it up?

This page tells you what product-signal does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.

Book a call →

The directory stays free. There is nothing gated behind this.