# Intel Discipline Advisor

Triage a competitive or market question into the right intelligence disciplines...

- Repository: https://github.com/deanpeters/Product-Manager-Skills (7825 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-10-16
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add deanpeters/Product-Manager-Skills --skill intel-discipline-advisor -g -a claude-code -y`
Codex: `npx skills add deanpeters/Product-Manager-Skills --skill intel-discipline-advisor -g -a codex -y`
Cursor: `npx skills add deanpeters/Product-Manager-Skills --skill intel-discipline-advisor -g -a cursor -y`
Gemini CLI: `npx skills add deanpeters/Product-Manager-Skills --skill intel-discipline-advisor -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add deanpeters/Product-Manager-Skills`

## Description

Triage a competitive or market question into the right intelligence disciplines, cadence, and executing skill. Use when you know something needs researching but not which channel to run.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Intel Discipline Advisor

## Purpose

Triage a competitive or market question into the right intelligence response: which of the eight
collection disciplines to run, on what cadence, feeding which artifact, executed by which skill. The
[`intelligence-collection-disciplines`](../intelligence-collection-disciplines/SKILL.md) compendium
holds everything about every channel; this advisor answers the question a busy PM actually has, *"given what's on my desk, which two or three channels matter, and where do my limited hours go?"*
Running every discipline on every question is the failure mode; scoping to the decision is the craft.
The advisor teaches the mapping as it routes, so by your third session you won't need it. That's the
goal.

## Input

**Works best with:** the decision or question on your desk, in your words, "I think [Competitor A]
is building something," "my TAM slide got shredded," "sales keeps getting surprised."
**Also useful:** any signal you've already noticed (a job posting, a pricing change, an earnings
remark), your time budget, and whether you're limited to free sources.

Anything supplied with the invocation itself, text after the skill name, a pasted context dump, or an
appended `ARGUMENTS:` line, counts as answers already given. Use it and skip whatever it covers;
don't re-ask.

**Arriving empty-handed? That works too.** The advisor opens by asking what's on your desk, with
enumerated situations to pick from.

**Example invocation:** `Intel discipline advisor: two of their senior engineers just followed our
CTO on a preprint server, and their careers page doubled, what do I run?`

## Key Concepts

The rest: https://github.com/deanpeters/Product-Manager-Skills/blob/HEAD/skills/intel-discipline-advisor/SKILL.md