intelligence-collection-disciplines

Structure competitive research across eight intelligence collection disciplines with signal-to-inference fusion.

6.8k|818|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/deanpeters/Product-Manager-Skills --skill intelligence-collection-disciplines
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: intelligence-collection-disciplines
Source: https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/intelligence-collection-disciplines
Command: npx skills add https://github.com/deanpeters/Product-Manager-Skills --skill intelligence-collection-disciplines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Single-source competitive research produces anecdotes, not intelligence. This Skill gives product managers the intelligence community's collection playbook: eight independent disciplines (OSINT, FININT, GEOINT/DEMOINT, TECHINT, HUMINT, SIGINT, MASINT, and all-source fusion) so weak signals from separate channels can be cross-validated into defensible conclusions.

Core Features & Use Cases

  • Eight Collection Disciplines: Each discipline lists free and paid sources, signal-to-inference chains, and the PM artifact it feeds (TAM/SAM/SOM, ICPs, battle cards, roadmap bets, pricing, positioning).
  • Confidence Stacking & Fusion: A fusion template applies the stacking rule — one discipline is a watch item, two a working hypothesis, three or more actionable intelligence — with a weekly/monthly/quarterly collection cadence.
  • Collection Plan Template & Worked Examples: A copy-paste plan with six instantiation variables ([TARGET], [MARKET], [GEOGRAPHY], [BUYER], [CAPABILITY], [DECISION]) plus fictional SaaS and industrial worked examples.
  • Use Case: You suspect a competitor is building a platform play. Fill the instantiation block, run HUMINT (hiring surge), TECHINT (patent cluster), and SIGINT (new subdomain cert), then fuse the signals into a high-confidence verdict that drives your roadmap response before their launch.

Quick Start

Use intelligence-collection-disciplines with [TARGET] set to your competitor, [CAPABILITY] set to the move you suspect, and [DECISION] set to what this research will change.

Frequently Asked Questions about intelligence-collection-disciplines

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run competitive research using intelligence collection disciplines?

Fill the six instantiation variables (target, market, geography, buyer, capability, decision), then select the two or three disciplines that feed your decision from the artifact-mapping table. Collect signals, label each as Fact, Inference, or Assumption, and fuse them with the confidence stacking rule.

What are OSINT, FININT, SIGINT, and MASINT in competitive intelligence?

They are independent collection channels: OSINT covers press and reviews, FININT covers filings and procurement, SIGINT covers website and pricing changes, and MASINT covers supply chain and facility indicators. Each fails differently, so agreement across channels signals a real finding.

How many signals do I need before acting on competitor intelligence?

The confidence stacking rule requires three or more independent disciplines telling one story before treating a conclusion as actionable. One discipline is a watch item, two form a working hypothesis, and conflicting signals mean you should dig deeper.

Is this kind of competitor research legal and ethical?

Yes, every source in the skill is published, filed, posted, or publicly observable, such as SEC filings, patent databases, job boards, and customs records. It explicitly prohibits pretexting, soliciting NDA-protected information, and scraping against agreed terms, referencing the SCIP Code of Ethics.

When should I not run all eight collection disciplines?

Never run all eight on one question. Choose only the disciplines that feed your specific decision using the artifact-mapping table, and match cadence to how fast each evidence channel changes, such as weekly for web diffs and annually for census-based sizing.