-
-
Notifications
You must be signed in to change notification settings - Fork 14
feat(cis): convert innovation strategy to a native skill #6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,6 @@ | ||
| --- | ||
| name: bmad-cis-innovation-strategy | ||
| description: '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"' | ||
| --- | ||
|
|
||
| Follow the instructions in [workflow.md](workflow.md). |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| type: skill |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,20 +1,59 @@ | ||
| # Innovation Strategy Workflow Instructions | ||
|
|
||
| <critical>The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml</critical> | ||
| <critical>You MUST have already loaded and processed: {project-root}/_bmad/cis/workflows/innovation-strategy/workflow.yaml</critical> | ||
| <critical>Load and understand innovation frameworks from: {innovation_frameworks}</critical> | ||
| <critical>⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever.</critical> | ||
| <critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.</critical> | ||
|
|
||
| <facilitation-principles> | ||
| YOU ARE A STRATEGIC INNOVATION ADVISOR: | ||
| - Demand brutal truth about market realities before innovation exploration | ||
| - Challenge assumptions ruthlessly - comfortable illusions kill strategies | ||
| - Balance bold vision with pragmatic execution | ||
| - Focus on sustainable competitive advantage, not clever features | ||
| - Push for evidence-based decisions over hopeful guesses | ||
| - Celebrate strategic clarity when achieved | ||
| </facilitation-principles> | ||
| --- | ||
| name: bmad-cis-innovation-strategy | ||
| description: '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"' | ||
| standalone: true | ||
| main_config: '{project-root}/_bmad/cis/config.yaml' | ||
| --- | ||
|
|
||
| # Innovation Strategy Workflow | ||
|
|
||
| **Goal:** Identify disruption opportunities and architect business model innovation through rigorous market analysis, option development, and execution planning. | ||
|
|
||
| **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. | ||
|
|
||
| --- | ||
|
|
||
| ## INITIALIZATION | ||
|
|
||
| ### Configuration Loading | ||
|
|
||
| Load config from `{main_config}` and resolve: | ||
|
|
||
| - `output_folder` | ||
| - `user_name` | ||
| - `communication_language` | ||
| - `date` as the system-generated current datetime | ||
|
|
||
| ### Paths | ||
|
|
||
| - `skill_path` = `{project-root}/_bmad/cis/workflows/bmad-cis-innovation-strategy` | ||
| - `template_file` = `./template.md` | ||
| - `innovation_frameworks_file` = `./innovation-frameworks.csv` | ||
| - `default_output_file` = `{output_folder}/innovation-strategy-{date}.md` | ||
|
|
||
| ### Inputs | ||
|
|
||
| - If the caller provides context via the data attribute, load it before Step 1 and use it to ground the session. | ||
| - Load and understand the full contents of `{innovation_frameworks_file}` before Step 2. | ||
| - Use `{template_file}` as the structure when writing `{default_output_file}`. | ||
|
|
||
| ### Behavioral Constraints | ||
|
|
||
| - Do not give time estimates. | ||
| - After every `<template-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. | ||
|
Comment on lines
+40
to
+43
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Resolve the time-estimate contradiction in the prompt contract. The global rule says not to give time estimates, but later steps ask for a 🧭 Suggested clarification- - Do not give time estimates.
+ - Do not give calendar dates or duration estimates unless the user explicitly asks.
+ - Sequencing work into relative phases is allowed.
...
- - Expected outcomes and timeline
+ - Expected outcomes and sequencing assumptionsAlso applies to: 212-220, 271-277 |
||
|
|
||
| ### Facilitation Principles | ||
|
|
||
| - Demand brutal truth about market realities before innovation exploration. | ||
| - Challenge assumptions ruthlessly; comfortable illusions kill strategies. | ||
| - Balance bold vision with pragmatic execution. | ||
| - Focus on sustainable competitive advantage, not clever features. | ||
| - Push for evidence-based decisions over hopeful guesses. | ||
| - Celebrate strategic clarity when achieved. | ||
|
|
||
| --- | ||
|
|
||
| ## EXECUTION | ||
|
|
||
| <workflow> | ||
|
|
||
|
|
@@ -42,7 +81,7 @@ Synthesize into clear strategic framing. | |
| <step n="2" goal="Analyze market landscape and competitive dynamics"> | ||
| Conduct thorough market analysis using strategic frameworks. Explain in your own voice why unflinching clarity about market realities must precede innovation exploration. | ||
|
|
||
| Review market analysis frameworks from {innovation_frameworks} (category: market_analysis) and select 2-4 most relevant to the strategic context. Consider: | ||
| Review market analysis frameworks from `{innovation_frameworks_file}` (category: market_analysis) and select 2-4 most relevant to the strategic context. Consider: | ||
|
|
||
| - Stage of business (startup vs established) | ||
| - Industry maturity | ||
|
|
@@ -77,7 +116,7 @@ Check in: "We've covered market landscape. How's your energy? This next part - d | |
|
|
||
| Deconstruct the existing business model to identify strengths and weaknesses. Explain in your own voice why understanding current model vulnerabilities is essential before innovation. | ||
|
|
||
| Review business model frameworks from {innovation_frameworks} (category: business_model) and select 2-3 appropriate for the business type. Consider: | ||
| Review business model frameworks from `{innovation_frameworks_file}` (category: business_model) and select 2-3 appropriate for the business type. Consider: | ||
|
|
||
| - Business maturity (early stage vs mature) | ||
| - Complexity of model | ||
|
|
@@ -107,7 +146,7 @@ Critical questions: | |
| <step n="4" goal="Identify disruption opportunities"> | ||
| Hunt for disruption vectors and strategic openings. Explain in your own voice what makes disruption different from incremental innovation. | ||
|
|
||
| Review disruption frameworks from {innovation_frameworks} (category: disruption) and select 2-3 most applicable. Consider: | ||
| Review disruption frameworks from `{innovation_frameworks_file}` (category: disruption) and select 2-3 most applicable. Consider: | ||
|
|
||
| - Industry disruption potential | ||
| - Customer job analysis needs | ||
|
|
@@ -141,7 +180,7 @@ Check in: "We've identified disruption vectors. How are you feeling? Ready to ge | |
|
|
||
| Develop concrete innovation options across multiple vectors. Explain in your own voice the importance of exploring multiple innovation paths before committing. | ||
|
|
||
| Review strategic and value_chain frameworks from {innovation_frameworks} (categories: strategic, value_chain) and select 2-4 that fit the strategic context. Consider: | ||
| Review strategic and value_chain frameworks from `{innovation_frameworks_file}` (categories: strategic, value_chain) and select 2-4 that fit the strategic context. Consider: | ||
|
|
||
| - Innovation ambition (core vs transformational) | ||
| - Value chain position | ||
|
|
||
This file was deleted.
This file was deleted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use a filesystem-safe timestamp for
default_output_file.dateis defined as the full current datetime and then interpolated directly into the filename. If that value includes:characters, the default save path will be invalid on Windows.🛠️ Suggested fix
📝 Committable suggestion
🤖 Prompt for AI Agents