@its-thepoe/market-command-matrix 1.0.0

package/README.md

@@ -0,0 +1,38 @@
+# @its-thepoe/market-command-matrix
+
+**Agent Skill** — **Market Command Matrix** (Patrick Campbell / Patticus): classify competitors by **market mindshare** and **resource strength**, interpret **market shape**, then pick **one primary motion** per priority player—attack, monitor, harvest, ignore, or partner—not a wallpaper of summaries.
+
+## What it does
+
+Builds **judgement upstream of action**: maps direct, adjacent, substitute, and ecosystem players; scores mindshare and resources (relative to your own market focus); places each player in the matrix; selects playbooks and concrete next moves with **evidence, confidence, and triggers**.
+
+## Why it’s useful
+
+- Stops at “here is what their website says” and forces **what to do** and **what to watch**.
+- Surfaces **harvest** and **monitor** opportunities teams often miss when everything feels like “compete.”
+- Separates **verified signals** from assumptions and ties actions to **checkpoints**.
+
+## Use when
+
+- Competitor research, **market mapping**, **positioning**, campaign or **GTM** prioritisation, **content wedges**, **sales battlecards**, **partnership** decisions, or recurring **market intelligence** reviews.
+
+## Install into your agents
+
+```bash
+npx @its-thepoe/skills@latest install market-command-matrix
+```
+
+## Contents
+
+- `SKILL.md` — workflow, model, completion gate  
+- `reference.md` — full playbooks, research steps, output templates, attribution  
+
+## Docs
+
+- [Patticus — Competitive research playbook (2023)](https://patticus.com/2023/12/16/competitive-research-playbook/)  
+- [kastrah/market-command-matrix (reference packaging)](https://github.com/kastrah/market-command-matrix)  
+- [Repository](https://github.com/its-thepoe/skills)
+
+## License
+
+MIT

package/SKILL.md

@@ -0,0 +1,87 @@
+---
+name: market-command-matrix
+version: "1.0"
+description: Turns competitor signals into judgement—mindshare vs resource strength, then attack/monitor/harvest/ignore/partner with one primary motion per priority player, not a research dump. Use for competitor analysis, market mapping, positioning, GTM prioritisation, battlecards, partnerships, content wedges, or market intelligence reviews.
+argument-hint: "[optional player name | format:full|one-page]"
+---
+
+# Market Command Matrix
+
+Goal: **intelligence upstream of action**—not competitor summaries for their own sake. Classify players, decide **what to do**, assign **owners and triggers**.
+
+## The model (two axes)
+
+**Market mindshare** — awareness, conversation, category association, unprompted recall, default comparisons when buyers think about the problem.
+
+**Resource strength** — capacity and focus **dedicated to winning this market** (funding, team, distribution, tech, partnerships, operational depth). Score **relative to market dedication**, not raw company size. Practical approach: score **your own** company 1–5 on focus and execution in this market, then score others **relative to you**.
+
+Each axis: **high / medium / low** (justify with evidence).
+
+## Decision categories
+
+| Category | Typical placement | One-line intent |
+|----------|-------------------|-----------------|
+| **All-out attack** | High mindshare + high resources | Sharp wedge, proof, channel discipline; expect retaliation. |
+| **Monitor** | Low mindshare + high resources | Watch capacity; triggers before overreacting. |
+| **Harvest** | High mindshare + low resources | Use their awareness; win on fulfilment, trust, depth, migration paths. |
+| **Ignore** | Low mindshare + low resources | No strategic energy; note customer signals only. |
+| **Partner** | Complementary / ecosystem | Integration, referral, co-marketing, bundling—define value exchange; watch channel conflict. |
+
+**Partner** is orthogonal to the 2×2; label when beating them is not required to win.
+
+## Competitor set (before matrix placement)
+
+Classify the **map** from the **customer view** of the market (buckets inform discovery; matrix uses mindshare + resources):
+
+1. **Direct** — same buyer, same JTBD, comparable promise; same budget or decision.
+2. **Adjacent** — overlapping workflow; could expand into your lane; partner and/or threat.
+3. **Substitute behaviours** — manual, informal, “good enough” habits instead of buying.
+4. **Ecosystem** — media, communities, platforms, agencies, infra that shape trust and access.
+
+## Workflow (run in order)
+
+### 1. Reconnaissance
+
+- Prefer **customer-led** signals: core **unaided** question first: *When you think of [CATEGORY], what is the first product that comes to mind?* Then aided recognition, usage, recommendation, value/friction.
+- Bias controls: unaided before aided; neutral framing where possible; separate **verified** evidence from assumptions.
+- Collect **current signals** per priority player (site messaging, product claims, social themes, ads, reviews, pricing/onboarding, press/partnerships, hiring/funding, SEO topics, FAQs/objections). Full list: [reference.md](reference.md#signal-checklist).
+
+### 2. Monitoring and extraction
+
+For each priority player, extract meaning: promise, ICP, lead pain, proof, CTA, strongest channel, what they avoid saying, visible operational weakness, behaviour they try to change. Questions: [reference.md](reference.md#extraction-questions).
+
+### 3. Matrix placement
+
+For each player: **category**, **rationale**, **confidence** (high/medium/low), **evidence used**, **what would change the placement**.
+
+### 4. Playbook selection
+
+**One primary motion per priority player.** Do not output a dump without decisions. Playbook menus: [reference.md](reference.md#playbooks-by-category).
+
+### 5. Market shape
+
+With enough coverage: **fragmented** | **challenger** | **ancient** | **mature**—and what that implies for offence vs defence. Definitions: [reference.md](reference.md#market-shapes).
+
+### 6. Whitespace and positioning
+
+Turn gaps into actions: underserved audience, weak promise, missing proof, poor follow-through, trust gap, channel mismatch, etc.
+
+## Output formats
+
+- **Full analysis:** strategic thesis, competitor map, evidence table, matrix placement, whitespace, recommended actions (owner, dependency, output, deadline), market shape, milestones/triggers. Skeleton: [reference.md](reference.md#full-analysis-template).
+- **One-page memo** (compressed): Player → Placement → Evidence (1–2 signals) → Meaning → Action → Trigger.
+
+Use `format:one-page` in the user request when they need the short memo only.
+
+## Completion gate (do not “finalize” without)
+
+- [ ] Competitor set classified (direct / adjacent / substitute / ecosystem as relevant).
+- [ ] Matrix category per **priority** player + rationale + confidence.
+- [ ] Evidence vs assumptions separated.
+- [ ] **One** selected primary playbook motion per priority player + **next action** + **checkpoint or trigger**.
+- [ ] Market-shape interpretation **if** enough players/data exist.
+- [ ] No “research only” handoff—every section ties to a **decision or motion**.
+
+## More detail
+
+Playbooks, market shapes, survey bias notes, Hermes install hint, sources: [reference.md](reference.md).

package/package.json

@@ -0,0 +1,21 @@
+{
+  "name": "@its-thepoe/market-command-matrix",
+  "version": "1.0.0",
+  "description": "Agent Skill: Market Command Matrix — mindshare vs resources, strategic playbooks (attack/monitor/harvest/ignore/partner).",
+  "license": "MIT",
+  "keywords": [
+    "agent-skills",
+    "competition",
+    "strategy",
+    "positioning",
+    "go-to-market",
+    "market-intelligence",
+    "cursor"
+  ],
+  "files": ["README.md", "SKILL.md", "reference.md", "package.json"],
+  "exports": {
+    ".": "./SKILL.md",
+    "./SKILL.md": "./SKILL.md",
+    "./reference.md": "./reference.md"
+  }
+}

package/reference.md

@@ -0,0 +1,191 @@
+# Market Command Matrix — reference
+
+Framework and narrative are based on **Patrick Campbell / Patticus**, [Competitor Research and Strategy (2023)](https://patticus.com/2023/12/16/competitive-research-playbook/). This package adapts that programme into a portable **Agent Skill**. A sibling-style repo with Hermes-oriented notes: [kastrah/market-command-matrix](https://github.com/kastrah/market-command-matrix).
+
+---
+
+## Signal checklist
+
+Use for reconnaissance and ongoing monitoring (monthly or quarterly cadence for priority players):
+
+- Website and landing-page messaging  
+- Product pages and feature claims  
+- Social profiles and recent themes  
+- Visible ads or campaign pushes  
+- App store listings and reviews (if relevant)  
+- Pricing and onboarding flow  
+- Press mentions and partnerships  
+- Hiring, funding, and expansion signals  
+- SEO / blog topics  
+- Customer comments, FAQs, repeated objections  
+
+Separate **verified** evidence from **assumptions**.
+
+---
+
+## Extraction questions
+
+For each priority player on each review cycle:
+
+1. What **promise** are they making?  
+2. Who are they **speaking to**?  
+3. What **pain** do they lead with?  
+4. What **proof** do they show?  
+5. What **CTA** do they push?  
+6. What **channel** are they strongest on?  
+7. What do they **avoid** saying?  
+8. What **operational weakness** is visible?  
+9. What **customer behaviour** are they trying to change?  
+
+---
+
+## Playbooks by category
+
+Pick **one primary motion** per priority player. Expand only where the user asks for depth.
+
+### Attack (high mindshare + high resources)
+
+- Comparison page or landing  
+- **Wedge** campaign (narrow audience, use case, geo, workflow, or belief gap)  
+- Proof-led positioning (claims competitors cannot copy quickly)  
+- Partnership attack (where legal and brand allow)  
+- Content wedge  
+- Sales battlecard  
+
+Expect retaliation or fast copying—discipline matters.
+
+### Monitor (low mindshare + high resources)
+
+- Monthly or quarterly **watchlist**  
+- Triggers: funding, hiring, pricing, messaging, partnerships, launches, channel moves  
+- Messaging change log  
+- Rules for when monitoring escalates to active competition  
+
+### Harvest (high mindshare + low resources)
+
+- Migration or switching offers  
+- Gap content (what they educate on vs what they under-deliver)  
+- Operational reliability proof, depth, support, trust  
+- Local execution story  
+- Integration strategy where relevant  
+
+### Ignore (low mindshare + low resources)
+
+- No strategic programme spend  
+- Capture any **useful customer signal** they reveal  
+- Revisit only if mindshare or resources shift materially  
+
+### Partner (ecosystem / complementary)
+
+- Ecosystem integration plan  
+- Referral or reseller path  
+- Joint campaign or audience swap  
+- Co-branded trust proof  
+- Clear value exchange; watch **channel conflict** and future competitive overlap  
+
+### Defend (when you are the incumbent under pressure)
+
+Use when **you** are the high-mindshare player under attack:
+
+- Retention messaging  
+- Customer education  
+- Objection handling  
+- Proof bank  
+- Reinforce switching costs **ethically** (real lock-in from value, not dark patterns)  
+
+---
+
+## Market shapes
+
+After matrix placement, name the **shape** when data supports it:
+
+| Shape | Read | Strategic implication (typical) |
+|-------|------|----------------------------------|
+| **Intensely fragmented** | No clear winner | If market is large/early, grow fast; if small/low-value, re-check opportunity sizing. |
+| **Challenger** | One or two dominant players | Attack leaders with wedges and/or partner other challengers. |
+| **Ancient** | Stagnant incumbents, poor CX | Harvest aggressively with fulfilment and trust. |
+| **Mature** | Active entrants and exits; mixed quadrants | Run **offensive and defensive** playbooks in parallel by segment. |
+
+---
+
+## Full analysis template
+
+Use as markdown sections unless the user’s org template overrides.
+
+### Strategic thesis
+
+One sentence: what the market map **means** for where to play and how to win.
+
+### Competitor map
+
+- Direct competitors  
+- Adjacent competitors  
+- Substitute behaviours  
+- Ecosystem actors  
+
+### Evidence table
+
+| Player | Signal | Source | Date checked | Confidence | Implication |
+|--------|--------|--------|--------------|------------|-------------|
+
+### Matrix placement
+
+| Player | Mindshare (H/M/L) | Resources (H/M/L) | Category | Rationale | What would change placement |
+|--------|-------------------|---------------------|----------|-----------|----------------------------|
+
+### Whitespace and positioning
+
+- What the market is missing  
+- What you can **credibly** own  
+- What **not** to copy  
+
+### Recommended actions
+
+| Action | Owner | Dependency | Output | Deadline / checkpoint |
+|--------|-------|------------|--------|-------------------------|
+
+### Market shape
+
+Fragmented / challenger / ancient / mature — and what that implies.
+
+### Milestones and triggers
+
+- What to monitor  
+- What would **change** the decision  
+- When to **re-run** the matrix  
+
+---
+
+## One-page decision memo template
+
+```text
+Player: …
+Placement: attack | monitor | harvest | ignore | partner
+Evidence: … (1–2 strongest signals)
+Meaning: … (what it changes strategically)
+Action: … (one concrete next move)
+Trigger: … (what to watch next)
+```
+
+---
+
+## Survey and research hygiene
+
+- **Unaided before aided** for mindshare questions.  
+- Avoid anchoring on your brand or a named competitor in early questions when possible.  
+- Prefer **anonymous or neutral** framing where compliance allows.  
+- Be careful with incentives (direct payment to panelists vs raffle-style bias).  
+- Survey sources (roughly easiest → hardest): your CRM/prospects (anonymous where possible), paid panels, prospects outside CRM (compliance), competitor customers from public proof, targeted ads to survey landers.  
+
+---
+
+## Hermes and other agents
+
+- **Hermes:** install by copying this skill folder (or `SKILL.md` + `reference.md`) into your Hermes skills directory; load skill name **`market-command-matrix`**.  
+- **Cursor / Claude Code / OpenCode / Windsurf:** use `npx @its-thepoe/skills@latest install market-command-matrix` (after publish) or symlink from this monorepo.
+
+---
+
+## License
+
+MIT — framework narrative credited to Patticus / Patrick Campbell as above; skill packaging under `@its-thepoe` is maintained in [its-thepoe/skills](https://github.com/its-thepoe/skills).