Skip to content

Agent-Engineer-Master/skill-engineer / strategy/industry-analysis/assess-strategic-environment

assess-strategic-environment

Unverified

Diagnoses competitive environment for an industry using BCG's Strategy Palette (Reeves) — Classical / Adaptive / Visionary / Shaping / Renewal — via the three-question discipline (predictability, malleability, harshness). Output: strategic-environment.md classifying the environment, evidencing the 3 dimensions with V/C/A/I tags, flagging ambidexterity, emitting a sub-skill routing matrix that weights Phase 1+2 sub-skills heavy/light/skip. Sub-skill of analyze-industry, invocable standalone. Runs FIRST in orchestrator chain — wrong diagnosis = wrong toolkit. Triggers on 'diagnose strategic environment for [industry]', 'strategy palette for [industry]', 'is [industry] classical or adaptive', 'classify the [industry] environment', 'Reeves environment for [industry]'. Do NOT activate for industry-attractiveness (use map-five-forces), market sizing (use size-market), single-company moat work (use assess-moat-sources), or DTC category go/no-go (use assess-category).

references/diagnostic-questions.md

View on GitHub
# Diagnostic Questions — the three-question discipline with anchors

Each dimension is rated High / Medium / Low, supported by at least one V/C/A/I-tagged evidence claim. Use these anchors as the structured prompts.

## Dimension 1 — Predictability

**Question:** Can the trajectory of this industry be reliably forecast over a 3-5 year horizon?

**Evidence anchors (cite at least one):**

| Anchor | High predictability | Low predictability |
|--------|---------------------|--------------------|
| Demand volatility (5yr CV) | <10% | >25% |
| Technology disruption cadence | New entrant / standard every 5+ years | New entrant / standard every <2 years |
| Regulatory landscape | Stable framework, known mandates | Active rulemaking, contested cases |
| Plausible 5yr scenarios | 1-2 (high-conviction central case) | 4+ (no consensus on which wins) |
| AI-native player share | <5% of market or absent | >10% and growing |

**Per-environment anchors:**
- **Classical** — Demand CV <10%, regulatory framework stable >10 years, no AI-native disruption [example: industrial gases]
- **Adaptive / Shaping** — Demand CV >25%, multiple plausible scenarios, AI-native players present [example: industrial robotics]
- **Visionary** — High predictability THAT THE TRAJECTORY EXISTS, even if details uncertain (e.g., GLP-1 demand wave was predictable from late-stage trials)

**Failure mode to avoid:** asserting "high predictability" because the industry feels boring. Boring ≠ predictable; some boring industries are quietly being unmade by AI.

## Dimension 2 — Malleability

**Question:** Can a single player (or a coordinated coalition) materially shape the industry's structure or rules?

**Evidence anchors (cite at least one):**

| Anchor | High malleability | Low malleability |
|--------|--------------------|---------------------|
| Platform dynamics | Two-sided market, network effects | One-sided, no NE |
| Concentration | One actor >25% share or de-facto standards | Fragmented, no anchor |
| Regulatory openness | Rulebook is being written, lobbying active | Rulebook locked, hard to change |
| Visible shaping moves | Consortia, standards bodies, ecosystem investments | None |
| Customer switching cost | Low (re-platformable) | High (locked-in, regulated) |

**Per-environment anchors:**
- **Classical / Adaptive** — fragmented players, no standards-setter, regulatory framework locked [example: industrial gases]
- **Visionary** — single player with technology + capital + vision to define the market [example: SpaceX in heavy-lift launch ~2015]
- **Shaping** — multiple players coordinating an ecosystem, no single shaper but a coalition can move the market [example: agentic commerce platforms in 2026]

**Failure mode to avoid:** declaring Visionary or Shaping based on founder rhetoric. Malleability is about *industry-level* shaping power, evidenced by visible moves and structural conditions. Default to Low unless positively evidenced.

## Dimension 3 — Harshness

**Question:** Is the industry in survival-mode — capital scarcity, regulatory cliff, demand collapse, or cost-curve collapse?

**Evidence anchors (cite at least one):**

| Trigger | Threshold for "Harsh" |
|---------|----------------------|
| Sustained negative growth | -3pp or worse, 2+ consecutive years |
| Capital markets closed | No funding rounds / IPOs / debt issuance in trailing 12mo; or repricings / bankruptcy waves |
| Existential regulation | Mandated wind-down, ban, license revocation pending |
| Cost > price | Sector-wide margins below cost-of-capital for 2+ years |

**Per-environment anchors:**
- **Renewal** — at least one of the four triggers, evidenced
- **NOT Renewal** — cyclical slowdown without structural cause, single-quarter weakness, individual firm distress in an otherwise-healthy sector

**Failure mode to avoid:** calling Renewal because last quarter looked rough. Harshness is structural and sustained.

## Decision matrix

| Predictability | Malleability | Harshness | → Environment |
|---|---|---|---|
| High | Low | Low | Classical |
| Low | Low | Low | Adaptive |
| High | High | Low | Visionary |
| Low | High | Low | Shaping |
| any | any | High | Renewal |

## Edge cases

**E1 — Mixed scoring (e.g., Predictability Medium):** Resolve by asking the tie-breaker: "If I had to pick a side, which way does the evidence lean?" If genuinely tied, declare ambidexterity (the industry is in transition).

**E2 — Multi-layer industry:** Semiconductors (fab vs fabless vs IP vs equipment) often sit in different environments per layer. Either restate intake to focal-layer OR declare ambidexterity with per-layer classifications.

**E3 — Geographic split:** A sector may be Classical in mature markets and Shaping in emerging ones. Default is to scope intake to one geography; if scope is global, declare ambidexterity.

**E4 — Transition in progress:** Industry was Classical for 30 years but is being unmade by AI in real-time. Classify by current state, but flag direction-of-travel in step 7.

**E5 — Visionary vs Shaping ambiguity:** Both have High malleability. The split is on predictability — Visionary has a clear endpoint visible (the founder can see it), Shaping does not. If you can't name the endpoint, it is Shaping, not Visionary.

## Ambidexterity discipline

Declare ambidexterity ONLY when:
1. The industry genuinely operates in two environments at named layers, geos, or segments AND
2. Each environment has its own evidenced classification AND
3. The split is structural, not transitional (transitional = single classification + direction-of-travel flag)

Format: "[Industry] exhibits ambidexterity: [Layer/Geo/Segment A] is [Environment 1] [evidence]; [Layer/Geo/Segment B] is [Environment 2] [evidence]. Downstream sub-skills must be scoped to one segment OR run twice."

Do not over-call. Most industries are single-environment when scoped correctly.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall