Orchestrate Porter Strategy

Orchestrate Porter Strategy

Route the user's request to the correct Porter skill(s) and chain outputs into a coherent analysis.

Skill Registry

Routing Rules

Step 1: Detect Entry Point

Match the user's request to one or more entry-point skills:

• Industry-level question → analyze-five-forces (then optionally diagnose-industry-type)
• Competitor question → profile-competitor (then optionally read-market-signals)
• Positioning question → map-strategic-groups
• "What strategy should we pursue?" → select-generic-strategy (needs five forces + groups first)
• Market entry question → analyze-market-entry
• Competitor action/signal → read-market-signals
• "How should we respond/attack?" → design-competitive-move (needs competitor profile first)
• "Is our strategy coherent?" → audit-strategy-consistency
• Industry type explicitly stated → route directly to strategize-{fragmented|emerging|declining}-industry

If ambiguous, ask: "Are you trying to understand the industry, analyze a competitor, choose a strategy, or plan a move?"

Step 2: Chain Outputs

After each skill completes, check if its output feeds a downstream skill:

Copy code
analyze-five-forces ──→ select-generic-strategy
                    ──→ analyze-market-entry
map-strategic-groups ──→ select-generic-strategy
diagnose-industry-type ──→ strategize-{fragmented|emerging|declining}-industry
profile-competitor ──→ read-market-signals
                   ──→ design-competitive-move
select-generic-strategy ──→ design-competitive-move
                        ──→ audit-strategy-consistency

Only chain if the user's question warrants it. Don't run the full DAG for a simple question.

Step 3: Skip Logic

• Skip a skill if its output is already supplied by the user
• Skip industry-type strategies if diagnose-industry-type classifies as "mature/stable" (no specialized strategy needed)
• Skip design-competitive-move unless the user has a specific action in mind

Workflow Shortcuts

For common multi-skill analyses, use these pre-built chains:

Quick Industry Check

analyze-five-forces → diagnose-industry-type → (route to industry-type skill if applicable) Trigger: "analyze this industry", "how attractive is this market?"

Competitor Deep Dive

profile-competitor → read-market-signals (if recent actions exist) Trigger: "analyze [competitor]", "what will [competitor] do?"

Should We Enter?

analyze-five-forces → analyze-market-entry Trigger: "should we enter [market]?", "entry barriers"

What Move?

profile-competitor → select-generic-strategy → design-competitive-move Trigger: "how should we compete?", "what move should we make?"

Full Strategic Audit

analyze-five-forces → map-strategic-groups → select-generic-strategy → audit-strategy-consistency Trigger: "full competitive analysis", "comprehensive strategy review"

Environment Assumptions

All skills assume: the user can provide an industry name and basic context; analysis is for a specific firm competing in the industry, not academic; data may be incomplete, so skills should note gaps rather than hallucinate.

Context Accumulation

As skills execute, accumulate their outputs in a running context object. Pass relevant prior outputs as input to downstream skills. Present the accumulated analysis to the user at the end.

Edge Cases

• Multiple industries: Run the chain separately for each, then compare
• Diversified firm: Run per-business-unit, noting corporate portfolio effects (from profile-competitor parent company analysis)
• No clear competitor: Start with analyze-five-forces and map-strategic-groups before attempting competitor analysis
• User wants everything: Use the Full Strategic Audit workflow, but warn it requires substantial input data