{"id":20487,"plugin_id":"plugins_6aa44273deb48191ac86b2dea87f3815","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:16:15.928Z","digest":"2d4ff86c9e24ff9b2b0a9aaecb003385f4c8120d3c49a0897aaa1b1f873adc5c","against":null,"payload":{"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.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":225},{"relative_path":"references/analysis-method.md","size_in_bytes":2245},{"relative_path":"references/visual-output.md","size_in_bytes":1550}],"name":"business-analysis","skill_md_contents":"---\nname: business-analysis\ndescription: 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.\n---\n\n# Business Engineer analysis\n\nBuild 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.\n\n## Retrieve before applying\n\nThe 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.\n\nThe 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.\n\n## Apply the method\n\nUse [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:\n\n- `routes` lists twelve authored decision paths; `routes <id>` returns one with its counter-lens.\n- `practice routing` maps decisions to source entries.\n- `get instrument:J` retrieves an instrument by letter; read its full body before applying it.\n- `practice engine` and `practice quality` return the source engine and checklist.\n\nFor 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.\n\nSeparate 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.\n\n## Deliver the result\n\nLead 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.\n\nFor 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.\n\nUse 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.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}