Competitive executive market brief skill

Prepare a concise, decision-oriented market and competitive brief for executives, leadership reviews, QBRs, board preparation, strategy discussions, or major planning moments.

by LMTYdotcom·MIT license·★ 29 Stars on the repo·GitHub ↗

Use now

Inside this skill

SKILL.md · the author's own words
# Competitive Executive Market Brief

## Mission

Turn market context into an executive decision surface.

The brief should tell leadership what changed, why it matters to the company's current priorities, what is uncertain, and which decisions o…

It should not be a compressed competitor newsletter.

## Use this skill when

- preparing for a board or leadership meeting
- creating a QBR competitive section
- briefing a CEO, CMO, CPO, CRO, or product leader
- a strategic planning cycle needs market context

Word-for-word excerpt, not a result. Read the full SKILL.md ↓

Files of Competitive executive market brief

LMTYdotcom/main1 file shown
SKILL.md
Show the full text237 lines

Competitive Executive Market Brief

Mission

Turn market context into an executive decision surface.

The brief should tell leadership what changed, why it matters to the company's current priorities, what is uncertain, and which decisions or questions deserve attention.

It should not be a compressed competitor newsletter.

Use this skill when

  • preparing for a board or leadership meeting
  • creating a QBR competitive section
  • briefing a CEO, CMO, CPO, CRO, or product leader
  • a strategic planning cycle needs market context
  • leadership asks "what changed and what should I care about?"
  • a PMM wants to prevent being blindsided in an executive conversation
  • a launch, pricing decision, or strategic shift needs executive market context

Do not use this skill when

  • the audience primarily wants operational weekly updates. Use competitive-market-briefing.
  • the user needs a full competitor teardown. Use competitive-deep-dive.
  • the user needs a detailed position, pricing, or launch work product. Use the corresponding skill, then summarize here.

Required outcome

Produce a brief that answers:

  1. What materially changed in the relevant period?
  2. Which changes matter to current company priorities?
  3. What market pattern or strategic implication is worth leadership attention?
  4. What is likely noise or not yet decision-relevant?
  5. What risks could surprise the company?
  6. What opportunities or openings may exist?
  7. Which assumptions are weak?
  8. What decisions, research, or monitoring should leadership authorize or discuss?

Context acquisition

Read references/CONTEXT.md. If call, CRM, win/loss or company-knowledge sources are connected, read references/INTERNAL.md before using them.

Minimum useful context:

  • company/product
  • meeting or audience
  • relevant time period if different from a sensible default

Strongly preferred:

  • company priorities, goals, or strategic motion
  • LMTY briefing and significant changes
  • current market report
  • product roadmap or launch context
  • revenue/deal/customer signals
  • prior leadership decisions when available

If current company priorities cannot be retrieved, ask only if the answer would materially alter the brief. Otherwise create a market-grounded brief and label the missing internal lens.

Source priority for this job

  1. current company priorities and decision context
  2. LMTY significant changes and briefing
  3. internal customer, deal, product, and revenue signals
  4. current report and competitor evidence
  5. external corroboration for material claims

Workflow

Step 1 - Identify the executive decision context

Determine:

  • audience
  • meeting type
  • current strategic priorities
  • decisions likely to be made
  • time horizon

A board brief and a product leadership QBR should select different market facts.

Step 2 - Gather significant market movement

Use LMTY briefing and change filters when available.

Prioritize:

  • pricing/packaging moves affecting economics or buyer expectations
  • product launches affecting differentiation or roadmap assumptions
  • positioning shifts affecting category narrative
  • target-customer movement
  • new entrants with actual evidence of relevance
  • market patterns supported by multiple signals

When internal sources exist, ask:

  • Are these changes appearing in deals?
  • Are customers asking for them?
  • Do they affect current launches or roadmap?
  • Do they affect strategic assumptions?
  • Do they alter the company's position or pricing narrative?

This step is what separates an executive brief from a news summary.

Step 4 - Prioritize by decision consequence

Rank items using:

  • potential business impact
  • relevance to current priority
  • evidence strength
  • time sensitivity
  • reversibility of a wrong decision

Do not rank by headline size or competitor fame.

Step 5 - Separate signal from noise

Include a short "not yet worth reacting to" section when the market is noisy.

This is useful executive value, especially when a Slack channel or news cycle is creating anxiety.

Step 6 - Surface risks and openings

Risks should be specific and evidence-linked.

Openings should be framed as hypotheses or questions unless customer/company evidence makes them stronger.

Step 7 - Create decision questions

A strong executive brief ends with a small number of questions such as:

  • Does this change an assumption behind our current pricing plan?
  • Do we need customer research before committing roadmap capacity?
  • Should we change launch language because our claimed difference is now parity?
  • Is this entrant appearing in enough deals to warrant active tracking?

Avoid generic "keep monitoring" as the only action.

Step 8 - Hand off what you do not own

Requests routinely arrive as two questions joined by "and". Answer the one this skill owns, in full. For the rest, name the skill that owns it and stop there.

This is not a refusal and it is not a disclaimer at the bottom. Write it as a line the reader can act on:

Pricing - the board question is really whether to change our pricing. That is a separate decision: run competitive-pricing-packaging-review with this analysis as input.

One line per area the work touched, named explicitly:

The request also wants Say to run
field talk tracks, objection handling, or a rep-facing card competitive-battlecard
a market position, messaging, or differentiation competitive-positioning
a full profile of one competitor competitive-deep-dive
launch framing, claims, or enablement for a release competitive-launch-readiness
a recurring digest of what changed competitive-market-briefing
whether a pattern is a real shift or noise competitive-market-shift-analysis
a pricing or packaging decision competitive-pricing-packaging-review

The failure this prevents is quietly answering the other half yourself. It looks helpful, and it produces a recommendation built on this skill's evidence alone, without the context the other decision actually needs.

Step 9 - Produce the artifact

Use assets/executive-brief-template.md.

Default length:

  • one page for leadership/QBR
  • up to two pages for board or strategy prep

Put source detail in an appendix.

Evidence and reasoning rules

Read references/TRUST.md.

Especially for executive briefs:

  • increase burden of proof as the decision consequence rises
  • do not hide contradictions
  • label speculative scenarios
  • distinguish "competitor moved" from "we need to respond"
  • preserve dates and freshness for material claims

Graceful fallback

Read references/DEGRADATION.md. For what LMTY can and cannot do, read references/LMTY.md.

Without company priorities:

  • produce a market-grounded brief
  • replace strong recommendations with decision questions

Without LMTY:

  • research a current snapshot and cite collection dates
  • avoid implying comprehensive monitored coverage

Composition

Each companion below owns a decision this skill should not make on its own evidence. The hand-off step is where the request's own follow-on question gets named.

Common inputs from:

  • competitive-market-briefing
  • competitive-market-shift-analysis
  • competitive-positioning
  • competitive-pricing-packaging-review
  • competitive-launch-readiness
  • competitive-deep-dive

Quality bar

Read references/QUALITY.md.

An executive should understand the decision landscape in under five minutes.

Every included item should answer "why is this in front of me?"

Examples of activating requests

  • "Prepare the competitive section for our QBR."
  • "I have a board meeting Friday. What market changes could blindside me?"
  • "Brief the CPO on what changed this quarter and the roadmap questions it raises."
  • "Turn this month's LMTY activity into a CEO-ready one-pager."
  • "What should leadership discuss based on the last 90 days of competitor movement?"

References

  • references/METHODOLOGY.md
  • references/LMTY.md
  • references/TRUST.md
  • references/CONTEXT.md
  • references/DEGRADATION.md
  • references/INTERNAL.md
  • references/QUALITY.md
1---
2name: competitive-executive-market-brief
3description: Prepare a concise, decision-oriented market and competitive brief for executives, leadership reviews, QBRs, board preparation, strategy discussions, or major planning moments. Use when leadership needs the few market changes, competitor moves, risks, opportunities, and decision questions that matter, with evidence and explicit uncertainty rather than a long CI report.
4license: MIT
5metadata:
6 author: LMTY
7 com.lmty.category: ci
8---
9 
10# Competitive Executive Market Brief
11 
12## Mission
13 
14Turn market context into an executive decision surface.
15 
16The brief should tell leadership what changed, why it matters to the company's current priorities, what is uncertain, and which decisions or questions deserve attention.
17 
18It should not be a compressed competitor newsletter.
19 
20## Use this skill when
21 
22- preparing for a board or leadership meeting
23- creating a QBR competitive section
24- briefing a CEO, CMO, CPO, CRO, or product leader
25- a strategic planning cycle needs market context
26- leadership asks "what changed and what should I care about?"
27- a PMM wants to prevent being blindsided in an executive conversation
28- a launch, pricing decision, or strategic shift needs executive market context
29 
30## Do not use this skill when
31 
32- the audience primarily wants operational weekly updates. Use `competitive-market-briefing`.
33- the user needs a full competitor teardown. Use `competitive-deep-dive`.
34- the user needs a detailed position, pricing, or launch work product. Use the corresponding skill, then summarize here.
35 
36## Required outcome
37 
38Produce a brief that answers:
39 
401. What materially changed in the relevant period?
412. Which changes matter to current company priorities?
423. What market pattern or strategic implication is worth leadership attention?
434. What is likely noise or not yet decision-relevant?
445. What risks could surprise the company?
456. What opportunities or openings may exist?
467. Which assumptions are weak?
478. What decisions, research, or monitoring should leadership authorize or discuss?
48 
49## Context acquisition
50 
51Read `references/CONTEXT.md`. If call, CRM, win/loss or company-knowledge sources are connected, read `references/INTERNAL.md` before using them.
52 
53Minimum useful context:
54- company/product
55- meeting or audience
56- relevant time period if different from a sensible default
57 
58Strongly preferred:
59- company priorities, goals, or strategic motion
60- LMTY briefing and significant changes
61- current market report
62- product roadmap or launch context
63- revenue/deal/customer signals
64- prior leadership decisions when available
65 
66If current company priorities cannot be retrieved, ask only if the answer would materially alter the brief. Otherwise create a market-grounded brief and label the missing internal lens.
67 
68## Source priority for this job
69 
701. current company priorities and decision context
712. LMTY significant changes and briefing
723. internal customer, deal, product, and revenue signals
734. current report and competitor evidence
745. external corroboration for material claims
75 
76## Workflow
77 
78### Step 1 - Identify the executive decision context
79 
80Determine:
81- audience
82- meeting type
83- current strategic priorities
84- decisions likely to be made
85- time horizon
86 
87A board brief and a product leadership QBR should select different market facts.
88 
89### Step 2 - Gather significant market movement
90 
91Use LMTY briefing and change filters when available.
92 
93Prioritize:
94- pricing/packaging moves affecting economics or buyer expectations
95- product launches affecting differentiation or roadmap assumptions
96- positioning shifts affecting category narrative
97- target-customer movement
98- new entrants with actual evidence of relevance
99- market patterns supported by multiple signals
100 
101### Step 3 - Link market movement to internal reality
102 
103When internal sources exist, ask:
104- Are these changes appearing in deals?
105- Are customers asking for them?
106- Do they affect current launches or roadmap?
107- Do they affect strategic assumptions?
108- Do they alter the company's position or pricing narrative?
109 
110This step is what separates an executive brief from a news summary.
111 
112### Step 4 - Prioritize by decision consequence
113 
114Rank items using:
115- potential business impact
116- relevance to current priority
117- evidence strength
118- time sensitivity
119- reversibility of a wrong decision
120 
121Do not rank by headline size or competitor fame.
122 
123### Step 5 - Separate signal from noise
124 
125Include a short "not yet worth reacting to" section when the market is noisy.
126 
127This is useful executive value, especially when a Slack channel or news cycle is creating anxiety.
128 
129### Step 6 - Surface risks and openings
130 
131Risks should be specific and evidence-linked.
132 
133Openings should be framed as hypotheses or questions unless customer/company evidence makes them stronger.
134 
135### Step 7 - Create decision questions
136 
137A strong executive brief ends with a small number of questions such as:
138- Does this change an assumption behind our current pricing plan?
139- Do we need customer research before committing roadmap capacity?
140- Should we change launch language because our claimed difference is now parity?
141- Is this entrant appearing in enough deals to warrant active tracking?
142 
143Avoid generic "keep monitoring" as the only action.
144 
145### Step 8 - Hand off what you do not own
146 
147Requests routinely arrive as two questions joined by "and". Answer the one this skill owns, in full. For the rest, name the skill that owns it and stop there.
148 
149This is not a refusal and it is not a disclaimer at the bottom. Write it as a line the reader can act on:
150 
151> **Pricing** - the board question is really whether to change our pricing. That is a separate decision: run `competitive-pricing-packaging-review` with this analysis as input.
152 
153One line per area the work touched, named explicitly:
154 
155| The request also wants | Say to run |
156| --- | --- |
157| field talk tracks, objection handling, or a rep-facing card | `competitive-battlecard` |
158| a market position, messaging, or differentiation | `competitive-positioning` |
159| a full profile of one competitor | `competitive-deep-dive` |
160| launch framing, claims, or enablement for a release | `competitive-launch-readiness` |
161| a recurring digest of what changed | `competitive-market-briefing` |
162| whether a pattern is a real shift or noise | `competitive-market-shift-analysis` |
163| a pricing or packaging decision | `competitive-pricing-packaging-review` |
164 
165The failure this prevents is quietly answering the other half yourself. It looks helpful, and it produces a recommendation built on this skill's evidence alone, without the context the other decision actually needs.
166 
167### Step 9 - Produce the artifact
168 
169Use `assets/executive-brief-template.md`.
170 
171Default length:
172- one page for leadership/QBR
173- up to two pages for board or strategy prep
174 
175Put source detail in an appendix.
176 
177## Evidence and reasoning rules
178 
179Read `references/TRUST.md`.
180 
181Especially for executive briefs:
182- increase burden of proof as the decision consequence rises
183- do not hide contradictions
184- label speculative scenarios
185- distinguish "competitor moved" from "we need to respond"
186- preserve dates and freshness for material claims
187 
188## Graceful fallback
189 
190Read `references/DEGRADATION.md`. For what LMTY can and cannot do, read `references/LMTY.md`.
191 
192Without company priorities:
193- produce a market-grounded brief
194- replace strong recommendations with decision questions
195 
196Without LMTY:
197- research a current snapshot and cite collection dates
198- avoid implying comprehensive monitored coverage
199 
200## Composition
201 
202Each companion below owns a decision this skill should not make on its own evidence. The hand-off step is where the request's own follow-on question gets named.
203 
204Common inputs from:
205- `competitive-market-briefing`
206- `competitive-market-shift-analysis`
207- `competitive-positioning`
208- `competitive-pricing-packaging-review`
209- `competitive-launch-readiness`
210- `competitive-deep-dive`
211 
212## Quality bar
213 
214Read `references/QUALITY.md`.
215 
216An executive should understand the decision landscape in under five minutes.
217 
218Every included item should answer "why is this in front of me?"
219 
220## Examples of activating requests
221 
222- "Prepare the competitive section for our QBR."
223- "I have a board meeting Friday. What market changes could blindside me?"
224- "Brief the CPO on what changed this quarter and the roadmap questions it raises."
225- "Turn this month's LMTY activity into a CEO-ready one-pager."
226- "What should leadership discuss based on the last 90 days of competitor movement?"
227 
228## References
229 
230- `references/METHODOLOGY.md`
231- `references/LMTY.md`
232- `references/TRUST.md`
233- `references/CONTEXT.md`
234- `references/DEGRADATION.md`
235- `references/INTERNAL.md`
236- `references/QUALITY.md`
237 

Discussion

Alternatives