Strategy Framework — Full Strategy Pipeline

Workflow

Phase 1: Preparation (Performed directly by the orchestrator)

1. Extract from user input:
   • Organization Info: Name, industry, size, current situation
   • Strategy Period: Annual/3-year/5-year
   • Existing Strategy Assets (optional): Existing OKRs, vision & mission, analytical materials
   • Special Requirements (optional): Emphasis on specific frameworks, focus on certain perspectives
2. Create the _workspace/ directory at the project root
3. Organize input and save as _workspace/00_input.md
4. If existing files are present, copy them to _workspace/ and skip the corresponding phase
5. Determine the execution mode based on request scope

Phase 2: Team Assembly and Execution

Tasks 2a (BSC) and 2b (SWOT) execute in parallel. Both depend only on Task 1 (OKR), so they can start simultaneously.

Inter-agent communication flow:

• okr-designer completes → sends OKR system to bsc-analyst; sends strategic assumptions to swot-specialist
• bsc-analyst completes → sends strategic blind spots to swot-specialist; sends KPI system to strategy-writer
• swot-specialist completes → sends TOWS strategy priorities to strategy-writer
• strategy-writer completes → sends all documents to strategy-reviewer
• strategy-reviewer cross-verifies all deliverables. When RED Must Fix items are found, sends revision requests to the relevant agent → rework → re-verify (up to 2 iterations)

Phase 3: Integration and Final Deliverables

1. Verify all files in _workspace/
2. Confirm that all RED Must Fix items from the review report have been addressed
3. Report the final summary to the user:
   • OKR Design Document — 01_okr_design.md
   • BSC Mapping Table — 02_bsc_mapping.md
   • SWOT Analysis Report — 03_swot_analysis.md
   • Vision & Mission Statement — 04_vision_mission.md
   • Strategy Execution Roadmap — 05_strategy_roadmap.md
   • Review Report — 06_review_report.md

Execution Modes by Request Scope

Existing file utilization: When the user provides existing files (OKR, SWOT, etc.), copy the file to the appropriate numbered position in _workspace/ and skip the corresponding agent's phase.

Data Transfer Protocol

File naming convention: {order_number}_{deliverable_name}.md

Error Handling

Test Scenarios

Normal Flow

Prompt: "Build a 2025 strategy framework for a Series B SaaS startup (50 employees). We're in the B2B HR tech space and want to grow ARR from $5M to $10M." Expected Result:

• OKR: 3-5 company-level Objectives + department-level cascading
• BSC: Four-perspective KPI mapping + strategy map, reflecting core SaaS metrics (ARR, NRR, CAC, LTV)
• SWOT: Reflecting HR tech industry trends, 5+ TOWS strategies
• Vision & Mission: Statements appropriate for a SaaS company
• Roadmap: Quarterly milestones + ARR growth trajectory

Existing File Flow

Prompt: "I've already done the SWOT analysis. Based on this, build the OKR, BSC, and roadmap." + attached SWOT file Expected Result:

• Copy the SWOT file to _workspace/03_swot_analysis.md
• Skip swot-specialist; deploy okr-designer + bsc-analyst + strategy-writer + reviewer
• Incorporate the existing SWOT's TOWS strategies into the OKR and roadmap

Error Flow

Prompt: "Build a strategy framework for our company" Expected Result:

• Insufficient organization info → Ask follow-up questions about industry/size/current situation
• If only minimal info (industry name) is provided, generate a hypothesis-based framework using benchmarks
• Tag all documents with "HYPOTHESIS-BASED — Needs validation with actual data"

Agent Extension Skills

Extension skills that enhance each agent's domain expertise: