The Business Engineer

View saved version →

---
name: business-analysis
description: Apply The Business Engineer methodology to a company, business model, competitive position, AI strategy, market, or operating decision. Use for strategic analysis and model application; use mental-models for a library lookup and visual-atlas for opening the existing Atlas.
---

# Business Engineer analysis

Build a defensible explanation that changes a decision. Infer the audience, decision owner, unit of analysis, and time horizon from the request. Respect requested brevity; use depth when the decision or evidence calls for it.

## Retrieve before applying

The plugin root is two directories above this skill directory. Use its `scripts/library.py` with Python 3; see [Library commands](../../references/library-commands.md). Search for the mechanism, then retrieve the full definitions of the selected entries. Usually a few complementary models and a credible counter-model are enough. Load neither `data/library.json` nor the complete source Markdown wholesale.

The current catalog contains 1,052 entries, including 261 core models, plus fifteen separate practice instruments. The earlier 258-concept ontology overlaps and uses different IDs. Read [Identity and evidence](../../references/identity-and-evidence.md) when working across editions, following redirects, or using numerical formulas. Never transfer an earlier concept number onto a core model with the same number.

## Apply the method

Use [The analytical engine](references/analysis-method.md) for substantial work. Retrieve a suitable instrument or guided path when it changes how the analysis is performed:

- `routes` lists twelve authored decision paths; `routes <id>` returns one with its counter-lens.
- `practice routing` maps decisions to source entries.
- `get instrument:J` retrieves an instrument by letter; read its full body before applying it.
- `practice engine` and `practice quality` return the source engine and checklist.

For each model, connect the mechanism to case evidence, identify the boundary or failure condition, and state its decision implication. Explain why differing lenses agree or conflict. Shared assumptions do not provide independent confirmation.

Separate observed facts, user context, inference, and hypotheses. Verify changing company, market, technical, legal, or financial facts using available primary sources. The bundled library supplies frameworks, not live business data. If access is missing, delimit the structural analysis and identify the missing evidence.

## Deliver the result

Lead with the conclusion, then explain its mechanism and evidence. Include the constraint, economic consequences, rival explanation, and what would change the decision when relevant. Use qualitative judgments unless numerical scales or calculations have a stated basis. Do not invent application steps for compressed source entries or promote proposed syntheses to established laws.

For a substantial strategic analysis, provide the written reasoning first and a faithful HTML visual after it, unless the user requests text only or another format. Read [Visual output](references/visual-output.md) only for that deliverable. Follow the environment's file-saving workflow for generated artifacts.

Use plain, precise language. Keep the user's requested tone and length. Attribute framework material to The Business Engineer and Gennaro Cuofano, and distinguish borrowed named frameworks from original syntheses.

Referenced files: 3

View saved version →

---
name: mental-models
description: Search, read, compare, and connect entries in The Business Engineer complete mental-models library. Use for a model name or ID, ontology navigation, source reconciliation, practice-instrument lookup, or selecting models for a decision.
---

# The complete mental-models library

Use the bundled retrieval script instead of reading the entire catalog into context. The plugin root is two directories above this skill directory. The command guide is [Library commands](../../references/library-commands.md).

A focused lookup usually needs:

1. `search "mechanism or name" --limit 8` to locate candidates.
2. `get <exact-ID>` to read the full definition, application, question, provenance, and retained earlier context.
3. `links <exact-ID>` when relationships matter.

Search defaults to the 1,052-entry consolidated catalog. Use `--collection core`, `disciplines`, `instruments`, `concepts`, or `all` deliberately. Search scores rank text matches; they are not confidence scores or proof that a model fits the case. Read full records before interpreting or comparing them.

## Identity and completeness

Read [Identity and evidence](../../references/identity-and-evidence.md) when working with source numbers, older entries, counts, or framework status.

- `core:137` and `BE-00-137` identify core model 137.
- `concept:137` and `BE-M0137` identify a different entry in the earlier ontology.
- `instrument:J` and `BE-P-J` identify practice instrument J.
- The script rejects a bare numeric ID because its namespace is ambiguous.
- Fifty previous IDs redirect to canonical homes and retain the earlier seat-specific text. Report that context when it materially differs.

For a broad decision, use `routes` or `practice routing` to find the relevant path and counter-lens. Retrieve only the required definitions and instruments. An authored route is a guide for inquiry, not a validated decision procedure.

For a model answer, explain the mechanism, useful conditions, boundary or falsifier, and one concrete application if requested. Preserve source attribution and epistemic status. Do not invent missing calibrations or claim every entry has empirical validation.

Use visual-atlas when the user wants the interactive library itself, and business-analysis when they want a full strategic application.

Referenced files: 1

View saved version →

---
name: visual-atlas
description: Open or export The Business Engineer complete interactive 3D Atlas, or take the user to a model, discipline, instrument, or guided path in it. Use for the existing visual library rather than creating a new strategic diagram.
---

# The visual Business Engineer Atlas

The plugin bundles `assets/Business-Engineer-Atlas.html`, the complete self-contained Atlas. The default Model library opens 3D; its 3D/List toggle shares the selected entry and filters. It contains the full 1,052-entry catalog, plus separate practice instruments and the earlier ontology.

The plugin root is two directories above this skill directory. Export with:

```sh
python3 <plugin-root>/scripts/library.py export atlas /absolute/output/Business-Engineer-Atlas.html
```

Use an actual writable artifact location selected by the host environment. The script refuses an existing output unless `--force` is supplied for an intended replacement. Follow the host's artifact-saving and delivery workflow. Do not link a cached skill directory as the user's output.

When requested, open the exported file using a supported user-facing artifact-opening capability. If that capability is absent, provide the file link without claiming it opened. No server, API key, or network request is required to run the exported Atlas.

For a particular model, resolve its exact ID with the library script, then use the returned `atlas_fragment`. Useful routes:

| Fragment | View |
| --- | --- |
| `#atlas` | Full 3D library |
| `#atlas?entry=BE-00-137` | Core model 137 in 3D |
| `#atlas?collection=core&part=II` | Core era models |
| `#atlas?collection=practice` | Practice instrument collection |
| `#atlas/library` | List view |
| `#atlas/map` | Discipline map |
| `#atlas/practice` | Operating instruments and engine |
| `#atlas/investigation?route=geopolitics` | Guided investigation |

If the artifact viewer cannot preserve fragments, provide the full Atlas and tell the user which model name to search. The lookup command uses `instruments`; the Atlas URL uses `practice`.

The package is a snapshot, not a live content-sync service. Saved investigations remain in the browser and origin that created them. The Atlas's Download investigation action preserves a portable analysis. Changes to the separate live site require an explicit site-editing task through the environment's site workflow.

Referenced files: 1