business-adventures-analysis-brooks

Name: business-adventures-analysis-brooks
Author: simbajigege

12installs21forks

How to install business-adventures-analysis-brooks?

simbajigege/book2skills/business-adventures-analysis-brooks

$npx -y skills add simbajigege/book2skills --skill business-adventures-analysis-brooks

Installs into the current project.

Summary

Use Business Adventures for "why did this fail?", "analyze this crisis", "what pattern applies?", or "what would Brooks notice?

Files · 1

View on GitHub

SKILL.md

1	# Business Adventures Analysis — Skill (John Brooks)
2
3	Knowledge source: Business Adventures by John Brooks.
4	Architecture: Orchestrator + 6 subskills. The main `SKILL.md` routes the user query; subskills execute the diagnostic workflows and own their reference IDs.
5
6	```text
7	business-adventures-analysis-brooks/
8	├── SKILL.md
9	├── quotes/
10	└── subskills/
11	├── m1_failure_diagnosis/
12	│ ├── module.md
13	│ └── references/case_library.md
14	├── m2_market_panic/
15	│ ├── module.md
16	│ └── references/case_library.md
17	├── m3_regulatory_risk/
18	│ ├── module.md
19	│ └── references/case_library.md
20	├── m4_product_innovation/
21	│ ├── module.md
22	│ └── references/case_library.md
23	├── m5_governance_accountability/
24	│ ├── module.md
25	│ └── references/case_library.md
26	└── m6_fraud_institutional_fragility/
27	├── module.md
28	└── references/case_library.md
29	```
30
31	## Skill Purpose
32
33	Use this skill to apply John Brooks's Business Adventures as a diagnostic framework for corporate failures, market panics, product launches, governance breakdowns, regulatory risk, fraud, innovation, and financial culture.
34
35	The skill does not summarize the book or predict the future by analogy. It maps a live business situation to recurring Brooks patterns: panic, hubris, communication failure, incentive drift, regulatory lag, product-market mismatch, and institutional fragility.
36
37	## Core Principle
38
39	Human nature is the constant; institutions are the variable. Identify the repeating human pattern first, then examine how structure, incentives, rules, timing, and information flow amplify it.
40
41	## Workflow Inventory
42
43	\| Workflow \| User question pattern \| Inputs \| Steps \| Output \| Should be subskill? \|
44	\|---\|---\|---\|---\|---\|---\|
45	\| Failure diagnosis \| "Why did this company, product, or strategy fail?" \| Company/product, timeline, market context, decisions \| Pattern map, decision chain, warning signals, preventable actions \| Primary failure pattern and decision correction \| Yes \|
46	\| Market panic analysis \| "What is happening in this crash?" \| Trigger, price moves, liquidity, media, forced sellers \| Panic phase, technical amplifiers, stabilizers, uncertainty \| Panic diagnosis and stabilizer map \| Yes \|
47	\| Regulatory risk review \| "Is this practice risky?" \| Practice, disclosure, materiality, enforcement context \| Materiality, public usability, tolerated-practice risk, rule-change trigger \| Risk level and action \| Yes \|
48	\| Product and innovation review \| "Will this launch or innovation work?" \| Product, customers, incumbents, distribution, research \| Timing test, differentiation, incumbent blind spots, commercialization \| Stop/redesign/accelerate/monitor recommendation \| Yes \|
49	\| Governance accountability \| "Is management handling this well?" \| Board, incentives, crisis response, shareholder/stakeholder power \| Formal power vs real consequences, incentives, accountability \| Governance diagnosis \| Yes \|
50	\| Fraud and institutional fragility \| "How exposed is this system?" \| Trust mechanism, counterparties, collateral, disclosure, losses \| Hidden exposure, responsibility transfer, contagion path, controls \| Fragility map and safeguards \| Yes \|
51
52	## When to Use This Skill
53
54	Invoke this skill when the user asks:
55
56	- "Why did this company, product, or strategy fail?"
57	- "Analyze this business case."
58	- "What historical pattern does this resemble?"
59	- "What would John Brooks say about this crisis?"
60	- "Is this governance, compliance, or regulatory behavior a warning sign?"
61	- "How do market panics typically unfold?"
62	- "What lessons from Edsel, Xerox, Texas Gulf Sulphur, Piggly Wiggly, or the 1962 crash apply here?"
63
64	## Routing Rules
65
66	\| User question type \| Must run \| Optional run \|
67	\|---\|---\|---\|
68	\| Broad case diagnosis or postmortem \| M1 Failure Diagnosis \| M3, M4, M5, or M6 depending on facts \|
69	\| Market crash, liquidity stress, speculative mania, selloff \| M2 Market Panic \| M6 if counterparties or technical systems are central \|
70	\| Insider information, disclosure, antitrust, tax, tolerated practice \| M3 Regulatory Risk \| M5 if board/executive accountability matters \|
71	\| Product launch, failed product, innovation, incumbent blindness \| M4 Product and Innovation \| M1 for full failure postmortem \|
72	\| Board conduct, shareholder power, executive accountability, crisis leadership \| M5 Governance Accountability \| M3 if legal exposure is material \|
73	\| Fraud, collateral failure, hidden exposure, systemic support, institutional trust \| M6 Fraud and Institutional Fragility \| M2 if panic dynamics are present \|
74	\| User asks only for historical parallel \| Run the closest single module \| M1 if the parallel needs a broader diagnosis \|
75
76	## Ex

People who liked this also viewed

6 picks

Type

business-adventures-analysis-brooks

12installs21forks

View on GitHub

How to install business-adventures-analysis-brooks?

simbajigege/book2skills/business-adventures-analysis-brooks

$npx -y skills add simbajigege/book2skills --skill business-adventures-analysis-brooks

Installs into the current project.

Summary

Use Business Adventures for "why did this fail?", "analyze this crisis", "what pattern applies?", or "what would Brooks notice?

Files · 1

View on GitHub

SKILL.md

1	# Business Adventures Analysis — Skill (John Brooks)
2
3	Knowledge source: Business Adventures by John Brooks.
4	Architecture: Orchestrator + 6 subskills. The main `SKILL.md` routes the user query; subskills execute the diagnostic workflows and own their reference IDs.
5
6	```text
7	business-adventures-analysis-brooks/
8	├── SKILL.md
9	├── quotes/
10	└── subskills/
11	├── m1_failure_diagnosis/
12	│ ├── module.md
13	│ └── references/case_library.md
14	├── m2_market_panic/
15	│ ├── module.md
16	│ └── references/case_library.md
17	├── m3_regulatory_risk/
18	│ ├── module.md
19	│ └── references/case_library.md
20	├── m4_product_innovation/
21	│ ├── module.md
22	│ └── references/case_library.md
23	├── m5_governance_accountability/
24	│ ├── module.md
25	│ └── references/case_library.md
26	└── m6_fraud_institutional_fragility/
27	├── module.md
28	└── references/case_library.md
29	```
30
31	## Skill Purpose
32
33	Use this skill to apply John Brooks's Business Adventures as a diagnostic framework for corporate failures, market panics, product launches, governance breakdowns, regulatory risk, fraud, innovation, and financial culture.
34
35	The skill does not summarize the book or predict the future by analogy. It maps a live business situation to recurring Brooks patterns: panic, hubris, communication failure, incentive drift, regulatory lag, product-market mismatch, and institutional fragility.
36
37	## Core Principle
38
39	Human nature is the constant; institutions are the variable. Identify the repeating human pattern first, then examine how structure, incentives, rules, timing, and information flow amplify it.
40
41	## Workflow Inventory
42
43	\| Workflow \| User question pattern \| Inputs \| Steps \| Output \| Should be subskill? \|
44	\|---\|---\|---\|---\|---\|---\|
45	\| Failure diagnosis \| "Why did this company, product, or strategy fail?" \| Company/product, timeline, market context, decisions \| Pattern map, decision chain, warning signals, preventable actions \| Primary failure pattern and decision correction \| Yes \|
46	\| Market panic analysis \| "What is happening in this crash?" \| Trigger, price moves, liquidity, media, forced sellers \| Panic phase, technical amplifiers, stabilizers, uncertainty \| Panic diagnosis and stabilizer map \| Yes \|
47	\| Regulatory risk review \| "Is this practice risky?" \| Practice, disclosure, materiality, enforcement context \| Materiality, public usability, tolerated-practice risk, rule-change trigger \| Risk level and action \| Yes \|
48	\| Product and innovation review \| "Will this launch or innovation work?" \| Product, customers, incumbents, distribution, research \| Timing test, differentiation, incumbent blind spots, commercialization \| Stop/redesign/accelerate/monitor recommendation \| Yes \|
49	\| Governance accountability \| "Is management handling this well?" \| Board, incentives, crisis response, shareholder/stakeholder power \| Formal power vs real consequences, incentives, accountability \| Governance diagnosis \| Yes \|
50	\| Fraud and institutional fragility \| "How exposed is this system?" \| Trust mechanism, counterparties, collateral, disclosure, losses \| Hidden exposure, responsibility transfer, contagion path, controls \| Fragility map and safeguards \| Yes \|
51
52	## When to Use This Skill
53
54	Invoke this skill when the user asks:
55
56	- "Why did this company, product, or strategy fail?"
57	- "Analyze this business case."
58	- "What historical pattern does this resemble?"
59	- "What would John Brooks say about this crisis?"
60	- "Is this governance, compliance, or regulatory behavior a warning sign?"
61	- "How do market panics typically unfold?"
62	- "What lessons from Edsel, Xerox, Texas Gulf Sulphur, Piggly Wiggly, or the 1962 crash apply here?"
63
64	## Routing Rules
65
66	\| User question type \| Must run \| Optional run \|
67	\|---\|---\|---\|
68	\| Broad case diagnosis or postmortem \| M1 Failure Diagnosis \| M3, M4, M5, or M6 depending on facts \|
69	\| Market crash, liquidity stress, speculative mania, selloff \| M2 Market Panic \| M6 if counterparties or technical systems are central \|
70	\| Insider information, disclosure, antitrust, tax, tolerated practice \| M3 Regulatory Risk \| M5 if board/executive accountability matters \|
71	\| Product launch, failed product, innovation, incumbent blindness \| M4 Product and Innovation \| M1 for full failure postmortem \|
72	\| Board conduct, shareholder power, executive accountability, crisis leadership \| M5 Governance Accountability \| M3 if legal exposure is material \|
73	\| Fraud, collateral failure, hidden exposure, systemic support, institutional trust \| M6 Fraud and Institutional Fragility \| M2 if panic dynamics are present \|
74	\| User asks only for historical parallel \| Run the closest single module \| M1 if the parallel needs a broader diagnosis \|
75
76	## Ex

People who liked this also viewed

6 picks

Type