/business-adventures-analysis-brooks

name: business-adventures-analysis-brooks
description: Use Business Adventures for "why did this fail?", "analyze this crisis", "what pattern applies?", or "what would Brooks notice?"
license: "Skill distillation for personal/educational use. Do not reproduce source passages verbatim."

Business Adventures Analysis — Skill (John Brooks)

**Knowledge source:** *Business Adventures* by John Brooks. **Architecture:** Orchestrator + 6 subskills. The main `SKILL.md` routes the user query; subskills execute the diagnostic workflows and own their reference IDs.

business-adventures-analysis-brooks/
├── SKILL.md
├── quotes/
└── subskills/
    ├── m1_failure_diagnosis/
    │   ├── module.md
    │   └── references/case_library.md
    ├── m2_market_panic/
    │   ├── module.md
    │   └── references/case_library.md
    ├── m3_regulatory_risk/
    │   ├── module.md
    │   └── references/case_library.md
    ├── m4_product_innovation/
    │   ├── module.md
    │   └── references/case_library.md
    ├── m5_governance_accountability/
    │   ├── module.md
    │   └── references/case_library.md
    └── m6_fraud_institutional_fragility/
        ├── module.md
        └── references/case_library.md

Skill Purpose

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.

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.

Core Principle

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.

Workflow Inventory

| Workflow | User question pattern | Inputs | Steps | Output | Should be subskill? | |---|---|---|---|---|---| | 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 | | 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 | | 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 | | 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 | | Governance accountability | "Is management handling this well?" | Board, incentives, crisis response, shareholder/stakeholder power | Formal power vs real consequences, incentives, accountability | Governance diagnosis | Yes | | 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 |

When to Use This Skill

Invoke this skill when the user asks:

• "Why did this company, product, or strategy fail?"
• "Analyze this business case."
• "What historical pattern does this resemble?"
• "What would John Brooks say about this crisis?"
• "Is this governance, compliance, or regulatory behavior a warning sign?"
• "How do market panics typically unfold?"
• "What lessons from Edsel, Xerox, Texas Gulf Sulphur, Piggly Wiggly, or the 1962 crash apply here?"

Routing Rules

| User question type | Must run | Optional run | |---|---|---| | Broad case diagnosis or postmortem | M1 Failure Diagnosis | M3, M4, M5, or M6 depending on facts | | Market crash, liquidity stress, speculative mania, selloff | M2 Market Panic | M6 if counterparties or technical systems are central | | Insider information, disclosure, antitrust, tax, tolerated practice | M3 Regulatory Risk | M5 if board/executive accountability matters | | Product launch, failed product, innovation, incumbent blindness | M4 Product and Innovation | M1 for full failure postmortem | | Board conduct, shareholder power, executive accountability, crisis leadership | M5 Governance Accountability | M3 if legal exposure is material | | Fraud, collateral failure, hidden exposure, systemic support, institutional trust | M6 Fraud and Institutional Fragility | M2 if panic dynamics are present | | User asks only for historical parallel | Run the closest single module | M1 if the parallel needs a broader diagnosis |

Execution Rules

1. Read only the modules required by the routing table. 2. If the user gives a broad failure question, run M1 first and then route to the most relevant specialist module. 3. If the user data is thin, ask for the missing timeline, actors, incentives, disclosures, and consequences before giving a confident diagnosis. 4. Do not run every module for a narrow question. 5. Use historical parallels as diagnostic lenses, not as predictions. 6. Each module owns its reference IDs in `references/case_library.md`; when citing Brooks-derived claims, use the IDs from the module actually run.

Multi-Module Output Format

## Brooks Pattern Diagnosis
- Situation:
- Primary module:
- Supporting modules:
- Active human pattern:
- Closest historical parallel:

## Diagnostic Chain
- Trigger:
- Decisions:
- Incentives:
- Amplifiers:
- Warning signals:
- Missing facts:

## Risk / Opportunity
- Current risk:
- Latent risk:
- Rule-maker, stabilizer, or accountable actor:
- What wo