Opportunity set
Skill codeeater/where-to-plai-plugin/plugins/where-to-plai/skills/opportunity-set
This skill should be used for Worksheet 1 of the Market Opportunity Navigator — generating a Market Opportunity Set. Triggers include "worksheet 1", "market opportunity set", "de-link our abilities", "re-link to applications", "brainstorm markets", "what markets could we serve", "find application and customer combinations", "generate opportunities for our technology". Use it to de-link the venture's core abilities from its product, re-link them into a varied set of application×customer opportunities, and screen down to ≈3–5.From its SKILL.md
npx -y skills add codeeater/where-to-plai-plugin --skill opportunity-setAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
5.6 KB, ~1.2k tokens by cl100k_base, as published. Nobody here has run it
Worksheet 1 — Market Opportunity Set
Help the team build a broad, varied set of market opportunities, then screen it down. A market opportunity = one application × one customer group, tied together by a need. The goal is cognitive flexibility — many viewpoints, not one early bet. The classic trap here is falling in love with the first idea, so coach the team to "look before you leap" — focusing from day one is a myth, and you never know what's out there unless you look.
Work with the team. Propose, prompt, and organise — but the team decides what enters and stays in their set.
The mechanic: de-link, then re-link
- De-linking (upper part): describe the venture's core abilities generically, separated from the current product — know-how, processes, rare resources, special capabilities. Ask "what can we do", not "what do we sell".
- Re-linking (lower part): for each ability (or combination), ask who has a need it could serve and what application would serve it. Deliberately reach for distant markets.
Procedure
-
De-link the abilities. Elicit the key elements: technological functions, unique know-how, processes, rare resources, existing strengths (customer base, channels, R&D). Describe each in the most generic terms and note its functions / properties / limitations. Allow hypothetical or planned abilities ("what if we also had X?"). Write these into the upper part of
where-to-play/01_opportunity-set.md. -
Re-link into opportunities. For each ability or recombination, brainstorm
application × customerpairs using the discovery prompts S&M lean on — "What can we do with this? Who may need this?" — and the Innovator's-DNA probes ("why, why not, what if"; "become an anthropologist"). Push for breadth and distance ("out of the box"). Use zoom-in / zoom-out to multiply segments. Separate buyer vs. user when they differ. Aim for a deliberately large brainstorm here (20–50 raw ideas is normal). To widen the search, optionally invoke theopportunity-discoveryagent for a breadth-first fan-out — it proposes candidates from distant domains; the team curates. -
Pick the right abstraction level ("continents vs. countries"). Keep all opportunities at a comparable granularity — specific enough to research and reach, not so narrow they fragment. Compare continents to continents, countries to countries.
-
Screen down (Initial Screening). Reduce the raw list to a handful using the four screening questions — apply them with the team, recording reasoning. Reassure them that dropping an option here is a win, not a loss: a "no-go" is a sign you searched broadly and creatively, and it is far cheaper to learn it now than after sweat, tears and money. Prefer a heterogeneous surviving set to maximise learning:
- Is there truly a customer need there?
- Can we satisfy this need with our unique abilities — and better than existing solutions? (treat as two checks)
- Are there severe restrictions that would hinder us from executing on this opportunity?
- Is this opportunity in line with our core values / moral compass?
-
Name and record the set. Give each surviving opportunity a clear, specific name. Target ≈3–5 ("a handful"). Write them into
where-to-play/01_opportunity-set.md. This set is a living document: opportunities can be added, refined, dismissed, or brought back — but a new one only enters after passing the screening above.
Optional: stage a quick debate
Worksheet 1 lives or dies on breadth, so a short two-sided debate helps. When the set feels thin or the team is anchored on one industry, offer to spawn the persona-explorer agent (push for bolder, more distant re-linking) and the persona-skeptic agent (stress-test the screening — is the need really a must-have, can you truly serve it better?). For a method-grounded nudge toward breadth, the advisor-tal-gruber agent in its "diverge" mode champions the opportunity landscape. These voices propose and provoke — the team still curates and screens.
Boundaries
- Generate candidates with the team and the discovery agent, but never lock the set yourself — the team curates and screens.
- A well-defined ability avoids vague labels like "algorithm" and never reveals how it works, only what it can do. A well-defined segment is specific enough that one could explain how to reach it.
- There is "no right or wrong" in the de-linking part — encourage divergence before screening.
Hand-off
When the set is named and screened, route to the attractiveness-map skill (Worksheet 2) to evaluate each opportunity.
Additional resources
references/worksheet-1-spec.md— full normative spec: de-/re-linking, abstraction level, the four screening questions, pitfalls, Innovator's-DNA discovery skills, open[[ZU PRÜFEN]]flags.references/examples/ceal-ws1.md— a real, filled Worksheet 1 (abilities + application×customer opportunities) as a few-shot reference.
What ships with it: 2 files
21.7 KB alongside SKILL.md
references/
- examples/ceal-ws1.md3.3 KB
- worksheet-1-spec.md18.4 KB