[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79RF4AV87WNPMQASYRBJ1HR":3,"skill-same:01M79RF4AV87WNPMQASYRBJ1HR":64},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M79RF4AV87WNPMQASYRBJ1HR","bmad-cis-innovation-strategy",null,"Identify disruption opportunities and architect business model innovation. Use when the user says \"lets create an innovation strategy\" or \"I want to find disruption opportunities\"","thkennedy\u002Ftk-studio","thkennedy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F4164502?v=4","01M79QZ8DMP5FF2HC6GS3S6FDF","Tim Kennedy","01M79QZ8EM9JBWJ15R5JNC4PW3",0,"MIT","https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fapps\u002Fsupervisor\u002F.claude\u002Fskills\u002Fbmad-cis-innovation-strategy\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: bmad-cis-innovation-strategy\ndescription: 'Identify disruption opportunities and architect business model innovation. Use when the user says \"lets create an innovation strategy\" or \"I want to find disruption opportunities\"'\n---\n\n# Innovation Strategy Workflow\n\n**Goal:** Identify disruption opportunities and architect business model innovation through rigorous market analysis, option development, and execution planning.\n\n**Your Role:** You are a strategic innovation advisor. Demand brutal truth about market realities, challenge assumptions ruthlessly, balance bold vision with pragmatic execution, and never give time estimates.\n\n## Conventions\n\n- Bare paths (e.g. `template.md`) resolve from the skill root.\n- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).\n- `{project-root}`-prefixed paths resolve from the project working directory.\n- `{skill-name}` resolves to the skill directory's basename.\n\n## On Activation\n\n### Step 1: Resolve the Workflow Block\n\nRun: `python3 {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow`\n\n**If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:\n\n1. `{skill-root}\u002Fcustomize.toml` — defaults\n2. `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.toml` — team overrides\n3. `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.user.toml` — personal overrides\n\nAny missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.\n\n### Step 2: Execute Prepend Steps\n\nExecute each entry in `{workflow.activation_steps_prepend}` in order before proceeding.\n\n### Step 3: Load Persistent Facts\n\nTreat every entry in `{workflow.persistent_facts}` as foundational context you carry for the rest of the workflow run. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. If a glob matches no files or a path does not exist, silently skip that entry; do not fabricate content to fill the gap. All other entries are facts verbatim.\n\n### Step 4: Load Config\n\nLoad config from `{project-root}\u002F_bmad\u002Fcis\u002Fconfig.yaml` and resolve:\n\n- `output_folder`\n- `user_name`\n- `communication_language`\n- `date` as the system-generated current datetime\n\n### Step 5: Greet the User\n\nGreet `{user_name}`, speaking in `{communication_language}`.\n\n### Step 6: Execute Append Steps\n\nExecute each entry in `{workflow.activation_steps_append}` in order.\n\nActivation is complete. Begin the workflow below.\n\n## Paths\n\n- `template_file` = `.\u002Ftemplate.md`\n- `innovation_frameworks_file` = `.\u002Finnovation-frameworks.csv`\n- `default_output_file` = `{output_folder}\u002Finnovation-strategy-{date}.md`\n\n## Inputs\n\n- If the caller provides context via the data attribute, load it before workflow Step 1 and use it to ground the session.\n- Load and understand the full contents of `{innovation_frameworks_file}` before workflow Step 2.\n- Use `{template_file}` as the structure when writing `{default_output_file}`.\n\n## Behavioral Constraints\n\n- Do not give time estimates.\n- After every `\u003Ctemplate-output>`, immediately save the current artifact to `{default_output_file}`, show a clear checkpoint separator, display the generated content, present options `[a] Advanced Elicitation`, `[c] Continue`, `[p] Party-Mode`, `[y] YOLO`, and wait for the user's response before proceeding.\n\n## Facilitation Principles\n\n- Demand brutal truth about market realities before innovation exploration.\n- Challenge assumptions ruthlessly; comfortable illusions kill strategies.\n- Balance bold vision with pragmatic execution.\n- Focus on sustainable competitive advantage, not clever features.\n- Push for evidence-based decisions over hopeful guesses.\n- Celebrate strategic clarity when achieved.\n\n## Execution\n\n\u003Cworkflow>\n\n\u003Cstep n=\"1\" goal=\"Establish strategic context\">\nUnderstand the strategic situation and objectives:\n\nAsk the user:\n\n- What company or business are we analyzing?\n- What's driving this strategic exploration? (market pressure, new opportunity, plateau, etc.)\n- What's your current business model in brief?\n- What constraints or boundaries exist? (resources, timeline, regulatory)\n- What would breakthrough success look like?\n\nLoad any context data provided via the data attribute.\n\nSynthesize into clear strategic framing.\n\n\u003Ctemplate-output>company_name\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>strategic_focus\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>current_situation\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>strategic_challenge\u003C\u002Ftemplate-output>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"2\" goal=\"Analyze market landscape and competitive dynamics\">\nConduct thorough market analysis using strategic frameworks. Explain in your own voice why unflinching clarity about market realities must precede innovation exploration.\n\nReview market analysis frameworks from `{innovation_frameworks_file}` (category: market_analysis) and select 2-4 most relevant to the strategic context. Consider:\n\n- Stage of business (startup vs established)\n- Industry maturity\n- Available market data\n- Strategic priorities\n\nOffer selected frameworks with guidance on what each reveals. Common options:\n\n- **TAM SAM SOM Analysis** - For sizing opportunity\n- **Five Forces Analysis** - For industry structure\n- **Competitive Positioning Map** - For differentiation analysis\n- **Market Timing Assessment** - For innovation timing\n\nKey questions to explore:\n\n- What market segments exist and how are they evolving?\n- Who are the real competitors (including non-obvious ones)?\n- What substitutes threaten your value proposition?\n- What's changing in the market that creates opportunity or threat?\n- Where are customers underserved or overserved?\n\n\u003Ctemplate-output>market_landscape\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>competitive_dynamics\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>market_opportunities\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>market_insights\u003C\u002Ftemplate-output>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"3\" goal=\"Analyze current business model\">\n\u003Cenergy-checkpoint>\nCheck in: \"We've covered market landscape. How's your energy? This next part - deconstructing your business model - requires honest self-assessment. Ready?\"\n\u003C\u002Fenergy-checkpoint>\n\nDeconstruct the existing business model to identify strengths and weaknesses. Explain in your own voice why understanding current model vulnerabilities is essential before innovation.\n\nReview business model frameworks from `{innovation_frameworks_file}` (category: business_model) and select 2-3 appropriate for the business type. Consider:\n\n- Business maturity (early stage vs mature)\n- Complexity of model\n- Key strategic questions\n\nOffer selected frameworks. Common options:\n\n- **Business Model Canvas** - For comprehensive mapping\n- **Value Proposition Canvas** - For product-market fit\n- **Revenue Model Innovation** - For monetization analysis\n- **Cost Structure Innovation** - For efficiency opportunities\n\nCritical questions:\n\n- Who are you really serving and what jobs are they hiring you for?\n- How do you create, deliver, and capture value today?\n- What's your defensible competitive advantage (be honest)?\n- Where is your model vulnerable to disruption?\n- What assumptions underpin your model that might be wrong?\n\n\u003Ctemplate-output>current_business_model\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>value_proposition\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>revenue_cost_structure\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>model_weaknesses\u003C\u002Ftemplate-output>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"4\" goal=\"Identify disruption opportunities\">\nHunt for disruption vectors and strategic openings. Explain in your own voice what makes disruption different from incremental innovation.\n\nReview disruption frameworks from `{innovation_frameworks_file}` (category: disruption) and select 2-3 most applicable. Consider:\n\n- Industry disruption potential\n- Customer job analysis needs\n- Platform opportunity existence\n\nOffer selected frameworks with context. Common options:\n\n- **Disruptive Innovation Theory** - For finding overlooked segments\n- **Jobs to be Done** - For unmet needs analysis\n- **Blue Ocean Strategy** - For uncontested market space\n- **Platform Revolution** - For network effect plays\n\nProvocative questions:\n\n- Who are the NON-consumers you could serve?\n- What customer jobs are massively underserved?\n- What would be \"good enough\" for a new segment?\n- What technology enablers create sudden strategic openings?\n- Where could you make the competition irrelevant?\n\n\u003Ctemplate-output>disruption_vectors\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>unmet_jobs\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>technology_enablers\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>strategic_whitespace\u003C\u002Ftemplate-output>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"5\" goal=\"Generate innovation opportunities\">\n\u003Cenergy-checkpoint>\nCheck in: \"We've identified disruption vectors. How are you feeling? Ready to generate concrete innovation opportunities?\"\n\u003C\u002Fenergy-checkpoint>\n\nDevelop concrete innovation options across multiple vectors. Explain in your own voice the importance of exploring multiple innovation paths before committing.\n\nReview strategic and value_chain frameworks from `{innovation_frameworks_file}` (categories: strategic, value_chain) and select 2-4 that fit the strategic context. Consider:\n\n- Innovation ambition (core vs transformational)\n- Value chain position\n- Partnership opportunities\n\nOffer selected frameworks. Common options:\n\n- **Three Horizons Framework** - For portfolio balance\n- **Value Chain Analysis** - For activity selection\n- **Partnership Strategy** - For ecosystem thinking\n- **Business Model Patterns** - For proven approaches\n\nGenerate 5-10 specific innovation opportunities addressing:\n\n- Business model innovations (how you create\u002Fcapture value)\n- Value chain innovations (what activities you own)\n- Partnership and ecosystem opportunities\n- Technology-enabled transformations\n\n\u003Ctemplate-output>innovation_initiatives\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>business_model_innovation\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>value_chain_opportunities\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>partnership_opportunities\u003C\u002Ftemplate-output>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"6\" goal=\"Develop and evaluate strategic options\">\nSynthesize insights into 3 distinct strategic options.\n\nFor each option:\n\n- Clear description of strategic direction\n- Business model implications\n- Competitive positioning\n- Resource requirements\n- Key risks and dependencies\n- Expected outcomes and timeline\n\nEvaluate each option against:\n\n- Strategic fit with capabilities\n- Market timing and readiness\n- Competitive defensibility\n- Resource feasibility\n- Risk vs reward profile\n\n\u003Ctemplate-output>option_a_name\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>option_a_description\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>option_a_pros\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>option_a_cons\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>option_b_name\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>option_b_description\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>option_b_pros\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>option_b_cons\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>option_c_name\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>option_c_description\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>option_c_pros\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>option_c_cons\u003C\u002Ftemplate-output>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"7\" goal=\"Recommend strategic direction\">\nMake bold recommendation with clear rationale.\n\nSynthesize into recommended strategy:\n\n- Which option (or combination) is recommended?\n- Why this direction over alternatives?\n- What makes you confident (and what scares you)?\n- What hypotheses MUST be validated first?\n- What would cause you to pivot or abandon?\n\nDefine critical success factors:\n\n- What capabilities must be built or acquired?\n- What partnerships are essential?\n- What market conditions must hold?\n- What execution excellence is required?\n\n\u003Ctemplate-output>recommended_strategy\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>key_hypotheses\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>success_factors\u003C\u002Ftemplate-output>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"8\" goal=\"Build execution roadmap\">\n\u003Cenergy-checkpoint>\nCheck in: \"We've got the strategy direction. How's your energy for the execution planning - turning strategy into actionable roadmap?\"\n\u003C\u002Fenergy-checkpoint>\n\nCreate phased roadmap with clear milestones.\n\nStructure in three phases:\n\n- **Phase 1 - Immediate Impact**: Quick wins, hypothesis validation, initial momentum\n- **Phase 2 - Foundation Building**: Capability development, market entry, systematic growth\n- **Phase 3 - Scale & Optimization**: Market expansion, efficiency gains, competitive positioning\n\nFor each phase:\n\n- Key initiatives and deliverables\n- Resource requirements\n- Success metrics\n- Decision gates\n\n\u003Ctemplate-output>phase_1\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>phase_2\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>phase_3\u003C\u002Ftemplate-output>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"9\" goal=\"Define metrics and risk mitigation\">\nEstablish measurement framework and risk management.\n\nDefine success metrics:\n\n- **Leading indicators** - Early signals of strategy working (engagement, adoption, efficiency)\n- **Lagging indicators** - Business outcomes (revenue, market share, profitability)\n- **Decision gates** - Go\u002Fno-go criteria at key milestones\n\nIdentify and mitigate key risks:\n\n- What could kill this strategy?\n- What assumptions might be wrong?\n- What competitive responses could occur?\n- How do we de-risk systematically?\n- What's our backup plan?\n\n\u003Ctemplate-output>leading_indicators\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>lagging_indicators\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>decision_gates\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>key_risks\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>risk_mitigation\u003C\u002Ftemplate-output>\n\n\u003Caction>Run: `python3 {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow.on_complete` — if the resolved value is non-empty, follow it as the final terminal instruction before exiting.\u003C\u002Faction>\n\u003C\u002Fstep>\n\n\u003C\u002Fworkflow>\n","# Innovation Strategy Workflow\n\n**Goal:** Identify disruption opportunities and architect business model innovation through rigorous market analysis, option development, and execution planning.\n\n**Your Role:** You are a strategic innovation advisor. Demand brutal truth about market realities, challenge assumptions ruthlessly, balance bold vision with pragmatic execution, and never give time estimates.\n\n## Conventions\n\n- Bare paths (e.g. `template.md`) resolve from the skill root.\n- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).\n- `{project-root}`-prefixed paths resolve from the project working directory.\n- `{skill-name}` resolves to the skill directory's basename.\n\n## On Activation\n\n### Step 1: Resolve the Workflow Block\n\nRun: `python3 {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow`\n\n**If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:\n\n1. `{skill-root}\u002Fcustomize.toml` — defaults\n2. `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.toml` — team overrides\n3. `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.user.toml` — personal overrides\n\nAny missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.\n\n### Step 2: Execute Prepend Steps\n\nExecute each entry in `{workflow.activation_steps_prepend}` in order before proceeding.\n\n### Step 3: Load Persistent Facts\n\nTreat every entry in `{workflow.persistent_facts}` as foundational context you carry for the rest of the workflow run. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. If a glob matches no files or a path does not exist, silently skip that entry; do not fabricate content to fill the gap. All other entries are facts verbatim.\n\n### Step 4: Load Config\n\nLoad config from `{project-root}\u002F_bmad\u002Fcis\u002Fconfig.yaml` and resolve:\n\n- `output_folder`\n- `user_name`\n- `communication_language`\n- `date` as the system-generated current datetime\n\n### Step 5: Greet the User\n\nGreet `{user_name}`, speaking in `{communication_language}`.\n\n### Step 6: Execute Append Steps\n\nExecute each entry in `{workflow.activation_steps_append}` in order.\n\nActivation is complete. Begin the workflow below.\n\n## Paths\n\n- `template_file` = `.\u002Ftemplate.md`\n- `innovation_frameworks_file` = `.\u002Finnovation-frameworks.csv`\n- `default_output_file` = `{output_folder}\u002Finnovation-strategy-{date}.md`\n\n## Inputs\n\n- If the caller provides context via the data attribute, load it before workflow Step 1 and use it to ground the session.\n- Load and understand the full contents of `{innovation_frameworks_file}` before workflow Step 2.\n- Use `{template_file}` as the structure when writing `{default_output_file}`.\n\n## Behavioral Constraints\n\n- Do not give time estimates.\n- After every `\u003Ctemplate-output>`, immediately save the current artifact to `{default_output_file}`, show a clear checkpoint separator, display the generated content, present options `[a] Advanced Elicitation`, `[c] Continue`, `[p] Party-Mode`, `[y] YOLO`, and wait for the user's response before proceeding.\n\n## Facilitation Principles\n\n- Demand brutal truth about market realities before innovation exploration.\n- Challenge assumptions ruthlessly; comfortable illusions kill strategies.\n- Balance bold vision with pragmatic execution.\n- Focus on sustainable competitive advantage, not clever features.\n- Push for evidence-based decisions over hopeful guesses.\n- Celebrate strategic clarity when achieved.\n\n## Execution\n\n\u003Cworkflow>\n\n\u003Cstep n=\"1\" goal=\"Establish strategic context\">\nUnderstand the strategic situation and objectives:\n\nAsk the user:\n\n- What company or business are we analyzing?\n- What's driving this strategic exploration? (market pressure, new opportunity, plateau, etc.)\n- What's your current business model in brief?\n- What constraints or boundaries exist? (resources, timeline, regulatory)\n- What would breakthrough success look like?\n\nLoad any context data provided via the data attribute.\n\nSynthesize into clear strategic framing.\n\n\u003Ctemplate-output>company_name\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>strategic_focus\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>current_situation\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>strategic_challenge\u003C\u002Ftemplate-output>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"2\" goal=\"Analyze market landscape and competitive dynamics\">\nConduct thorough market analysis using strategic frameworks. Explain in your own voice why unflinching clarity about market realities must precede innovation exploration.\n\nReview market analysis frameworks from `{innovation_frameworks_file}` (category: market_analysis) and select 2-4 most relevant to the strategic context. Consider:\n\n- Stage of business (startup vs established)\n- Industry maturity\n- Available market data\n- Strategic priorities\n\nOffer selected frameworks with guidance on what each reveals. Common options:\n\n- **TAM SAM SOM Analysis** - For sizing opportunity\n- **Five Forces Analysis** - For industry structure\n- **Competitive Positioning Map** - For differentiation analysis\n- **Market Timing Assessment** - For innovation timing\n\nKey questions to explore:\n\n- What market segments exist and how are they evolving?\n- Who are the real competitors (including non-obvious ones)?\n- What substitutes threaten your value proposition?\n- What's changing in the market that creates opportunity or threat?\n- Where are customers underserved or overserved?\n\n\u003Ctemplate-output>market_landscape\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>competitive_dynamics\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>market_opportunities\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>market_insights\u003C\u002Ftemplate-output>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"3\" goal=\"Analyze current business model\">\n\u003Cenergy-checkpoint>\nCheck in: \"We've covered market landscape. How's your energy? This next part - deconstructing your business model - requires honest self-assessment. Ready?\"\n\u003C\u002Fenergy-checkpoint>\n\nDeconstruct the existing business model to identify strengths and weaknesses. Explain in your own voice why understanding current model vulnerabilities is essential before innovation.\n\nReview business model frameworks from `{innovation_frameworks_file}` (category: business_model) and select 2-3 appropriate for the business type. Consider:\n\n- Business maturity (early stage vs mature)\n- Complexity of model\n- Key strategic questions\n\nOffer selected frameworks. Common options:\n\n- **Business Model Canvas** - For comprehensive mapping\n- **Value Proposition Canvas** - For product-market fit\n- **Revenue Model Innovation** - For monetization analysis\n- **Cost Structure Innovation** - For efficiency opportunities\n\nCritical questions:\n\n- Who are you really serving and what jobs are they hiring you for?\n- How do you create, deliver, and capture value today?\n- What's your defensible competitive advantage (be honest)?\n- Where is your model vulnerable to disruption?\n- What assumptions underpin your model that might be wrong?\n\n\u003Ctemplate-output>current_business_model\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>value_proposition\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>revenue_cost_structure\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>model_weaknesses\u003C\u002Ftemplate-output>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"4\" goal=\"Identify disruption opportunities\">\nHunt for disruption vectors and strategic openings. Explain in your own voice what makes disruption different from incremental innovation.\n\nReview disruption frameworks from `{innovation_frameworks_file}` (category: disruption) and select 2-3 most applicable. Consider:\n\n- Industry disruption potential\n- Customer job analysis needs\n- Platform opportunity existence\n\nOffer selected frameworks with context. Common options:\n\n- **Disruptive Innovation Theory** - For finding overlooked segments\n- **Jobs to be Done** - For unmet needs analysis\n- **Blue Ocean Strategy** - For uncontested market space\n- **Platform Revolution** - For network effect plays\n\nProvocative questions:\n\n- Who are the NON-consumers you could serve?\n- What customer jobs are massively underserved?\n- What would be \"good enough\" for a new segment?\n- What technology enablers create sudden strategic openings?\n- Where could you make the competition irrelevant?\n\n\u003Ctemplate-output>disruption_vectors\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>unmet_jobs\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>technology_enablers\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>strategic_whitespace\u003C\u002Ftemplate-output>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"5\" goal=\"Generate innovation opportunities\">\n\u003Cenergy-checkpoint>\nCheck in: \"We've identified disruption vectors. How are you feeling? Ready to generate concrete innovation opportunities?\"\n\u003C\u002Fenergy-checkpoint>\n\nDevelop concrete innovation options across multiple vectors. Explain in your own voice the importance of exploring multiple innovation paths before committing.\n\nReview strategic and value_chain frameworks from `{innovation_frameworks_file}` (categories: strategic, value_chain) and select 2-4 that fit the strategic context. Consider:\n\n- Innovation ambition (core vs transformational)\n- Value chain position\n- Partnership opportunities\n\nOffer selected frameworks. Common options:\n\n- **Three Horizons Framework** - For portfolio balance\n- **Value Chain Analysis** - For activity selection\n- **Partnership Strategy** - For ecosystem thinking\n- **Business Model Patterns** - For proven approaches\n\nGenerate 5-10 specific innovation opportunities addressing:\n\n- Business model innovations (how you create\u002Fcapture value)\n- Value chain innovations (what activities you own)\n- Partnership and ecosystem opportunities\n- Technology-enabled transformations\n\n\u003Ctemplate-output>innovation_initiatives\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>business_model_innovation\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>value_chain_opportunities\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>partnership_opportunities\u003C\u002Ftemplate-output>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"6\" goal=\"Develop and evaluate strategic options\">\nSynthesize insights into 3 distinct strategic options.\n\nFor each option:\n\n- Clear description of strategic direction\n- Business model implications\n- Competitive positioning\n- Resource requirements\n- Key risks and dependencies\n- Expected outcomes and timeline\n\nEvaluate each option against:\n\n- Strategic fit with capabilities\n- Market timing and readiness\n- Competitive defensibility\n- Resource feasibility\n- Risk vs reward profile\n\n\u003Ctemplate-output>option_a_name\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>option_a_description\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>option_a_pros\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>option_a_cons\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>option_b_name\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>option_b_description\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>option_b_pros\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>option_b_cons\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>option_c_name\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>option_c_description\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>option_c_pros\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>option_c_cons\u003C\u002Ftemplate-output>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"7\" goal=\"Recommend strategic direction\">\nMake bold recommendation with clear rationale.\n\nSynthesize into recommended strategy:\n\n- Which option (or combination) is recommended?\n- Why this direction over alternatives?\n- What makes you confident (and what scares you)?\n- What hypotheses MUST be validated first?\n- What would cause you to pivot or abandon?\n\nDefine critical success factors:\n\n- What capabilities must be built or acquired?\n- What partnerships are essential?\n- What market conditions must hold?\n- What execution excellence is required?\n\n\u003Ctemplate-output>recommended_strategy\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>key_hypotheses\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>success_factors\u003C\u002Ftemplate-output>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"8\" goal=\"Build execution roadmap\">\n\u003Cenergy-checkpoint>\nCheck in: \"We've got the strategy direction. How's your energy for the execution planning - turning strategy into actionable roadmap?\"\n\u003C\u002Fenergy-checkpoint>\n\nCreate phased roadmap with clear milestones.\n\nStructure in three phases:\n\n- **Phase 1 - Immediate Impact**: Quick wins, hypothesis validation, initial momentum\n- **Phase 2 - Foundation Building**: Capability development, market entry, systematic growth\n- **Phase 3 - Scale & Optimization**: Market expansion, efficiency gains, competitive positioning\n\nFor each phase:\n\n- Key initiatives and deliverables\n- Resource requirements\n- Success metrics\n- Decision gates\n\n\u003Ctemplate-output>phase_1\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>phase_2\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>phase_3\u003C\u002Ftemplate-output>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"9\" goal=\"Define metrics and risk mitigation\">\nEstablish measurement framework and risk management.\n\nDefine success metrics:\n\n- **Leading indicators** - Early signals of strategy working (engagement, adoption, efficiency)\n- **Lagging indicators** - Business outcomes (revenue, market share, profitability)\n- **Decision gates** - Go\u002Fno-go criteria at key milestones\n\nIdentify and mitigate key risks:\n\n- What could kill this strategy?\n- What assumptions might be wrong?\n- What competitive responses could occur?\n- How do we de-risk systematically?\n- What's our backup plan?\n\n\u003Ctemplate-output>leading_indicators\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>lagging_indicators\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>decision_gates\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>key_risks\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>risk_mitigation\u003C\u002Ftemplate-output>\n\n\u003Caction>Run: `python3 {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow.on_complete` — if the resolved value is non-empty, follow it as the final terminal instruction before exiting.\u003C\u002Faction>\n\u003C\u002Fstep>\n\n\u003C\u002Fworkflow>\n",{"name":5,"description":7},"main","ecd23b3c0458cd511812f643d9111e3d7c8235f4","apps\u002Fsupervisor\u002F.claude\u002Fskills\u002Fbmad-cis-innovation-strategy","https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio","https:\u002F\u002Fgithub.com\u002Fthkennedy","https:\u002F\u002Ftimothyhkennedy.com","Just a guy who loves making tools, automation and games.","2026-11-10 20:38:16",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add thkennedy\u002Ftk-studio --skill bmad-cis-innovation-strategy",{"tool":38,"command":39},"bunx","bunx skills add thkennedy\u002Ftk-studio --skill bmad-cis-innovation-strategy",{"tool":41,"command":42},"pnpm","pnpm dlx skills add thkennedy\u002Ftk-studio --skill bmad-cis-innovation-strategy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fapps\u002Fsupervisor\u002F.claude\u002Fskills\u002Fbmad-cis-innovation-strategy\u002FSKILL.md",true,[46,52,58],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"customize.toml","OTHER","其他",1724,"https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fapps\u002Fsupervisor\u002F.claude\u002Fskills\u002Fbmad-cis-innovation-strategy\u002Fcustomize.toml",{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"innovation-frameworks.csv","ASSET","资产文件",8453,"https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fapps\u002Fsupervisor\u002F.claude\u002Fskills\u002Fbmad-cis-innovation-strategy\u002Finnovation-frameworks.csv",{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"template.md","REFERENCE","参考文档",2374,"https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fapps\u002Fsupervisor\u002F.claude\u002Fskills\u002Fbmad-cis-innovation-strategy\u002Ftemplate.md",[65,72,79,86,93,100],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M79RYSQ8C3MWDFTDSRAYFJYA","tk-studio-track","Tracking verbs on the bound Jira project — `block` moves a story the loop cannot progress, and each dependent story, to \"Blocked - Awaiting User\" with a comment that @mentions the owner (or, with `--engagement`, one engagement's questions issue, which `close` later moves to \"Done\"); `reply` posts the owner's answer (or \"Done.\") with the owner's host-only token and moves the issue to \"Block Resolved\"; `validate` checks that resolution and passes the issue back to work or re-blocks it with a follow-up. Use when the user says \"block this story\", \"tk track block\", \"put it in the owner's inbox\", \"reply to the blocked issue\", \"validate the resolution\", or a supervisor or engagement payload names this skill.","https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fplugins\u002Ftk-studio\u002Fskills\u002Ftk-studio-track\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M79RYMVE0031EV5B64MBGD8V","tk-studio-session","Session discipline as a surface — land a boundary handoff (optionally carrying knowledge deltas) and end the session, or resume a fresh session from a run workspace alone. Use when the user says \"hand off this run\", \"tk session\", \"resume the run\", or a boundary\u002Fbudget trigger says the session must split.","https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fplugins\u002Ftk-studio\u002Fskills\u002Ftk-studio-session\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M79RYFM9ATWHM6HAXJ3D19WV","tk-studio-research","Run a chartered research pass — survey the topics a charter scopes, grade every finding by evidence, land the findings in the run workspace, and emit observation events for recommendation-worthy ones. Use when the user says \"run the ecosystem watch\", \"tk research\", or a research job's invoke-skill directive names this skill.","https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fplugins\u002Ftk-studio\u002Fskills\u002Ftk-studio-research\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M79RYA1AWZZF83KBHGR6JDN3","tk-studio-report","One-verb human defect report — \"the skill did the wrong thing\" — recorded as a report event in the local measurement ledger. Use when the user says \"tk report\", \"report a defect\", \"that skill misbehaved\", or \"log a studio issue\".","https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fplugins\u002Ftk-studio\u002Fskills\u002Ftk-studio-report\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M79RY33VMYR5YNPVFKWRNW9S","tk-studio-playable-judge","The playable-verify leg's screenshot judge (Story 34.3) — reads only a playable run's report.json and its frames, answers the fixed rubric (scene loaded, player visible and framed, no magenta or error overlay, HUD reads, the named moments shown) with pass or fail and findings each naming a frame and a rubric line. Driven headless by the supervisor's host leg on the project's sandbox tier; use when the payload names a playable `media` folder, or the user says \"judge the playable frames\".","https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fplugins\u002Ftk-studio\u002Fskills\u002Ftk-studio-playable-judge\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M79RXY4AM8JM6ZK2MAR3W3X2","tk-studio-plan-sync","Planning adapter — canonicalize BMad-native planning artifacts (normalize pass, sole id authority) and sync them with the bound planning backend. Use when the user says \"sync the plan\", \"normalize planning artifacts\", \"tk plan sync\", or after stock BMad planning flows produce or change epics\u002Fstories.","https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fplugins\u002Ftk-studio\u002Fskills\u002Ftk-studio-plan-sync\u002FSKILL.md",[],[]]