mirror of
https://github.com/MaksTinyWorkshop/_Assistant_Lead_Tech
synced 2026-06-28 01:53:40 +02:00
chore(bmad): migrate 80_bmad/base from 6.0.4 to 6.9 + port customizations to TOML overrides
Migration des modules via l'installer officiel (Quick update, en place) : - core/bmm 6.0.4 -> 6.9.0 - tea 1.5.3 -> 1.19.0 - cis 0.1.8 -> 0.2.1 Portage des customisations Lead_tech vers le nouveau mécanisme d'overrides (_bmad/custom/<skill>.toml, couche "team" résolue par resolve_customization.py) : - 6 agents directs (analyst, architect, dev, pm, tech-writer, ux-designer) - module tea - workflows: dev-story, create-story, code-review, quick-dev, qa-generate-e2e-tests - agents disparus en 6.9 reportés vers leurs workflows hôtes (QA -> code-review, SM -> create-story, quick-flow-solo-dev -> quick-dev) - règle de capitalisation 95_a_capitaliser factorisée dans _bmad/custom/leadtech-capitalisation.md (référencée via persistent_facts) Nettoyage du legacy 6.0.4 : - suppression des 17 *.customize.yaml (non lus par 6.9) - suppression des .bak générés par l'installer (contenu porté en .toml) - suppression de 17 skills orphelins dans .agents/skills (anciens noms, .agents/.claude réalignés 66=66) - suppression des coquilles de workflows disparus Tous les overrides validés par le resolver officiel (12/12 JSON valide, base préservée + ajouts Lead_tech). Le cœur (couche customize.toml) n'est plus modifié, donc les updates 6.x futurs ne pourront plus écraser ces customisations. Note env: resolve_customization.py exige Python >=3.11 (uv installé, python3 -> 3.12.13). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
MaksTinyWorkshop
@@ -1,14 +1,274 @@
|
||||
---
|
||||
name: bmad-cis-design-thinking
|
||||
description: Guide human-centered design processes using empathy-driven methodologies. Use when the user says "lets run design thinking" or "I want to apply design thinking"
|
||||
description: 'Guide human-centered design processes using empathy-driven methodologies. Use when the user says "lets run design thinking" or "I want to apply design thinking"'
|
||||
---
|
||||
|
||||
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
|
||||
# Design Thinking Workflow
|
||||
|
||||
<steps CRITICAL="TRUE">
|
||||
1. Always LOAD the FULL {project-root}/_bmad/core/tasks/workflow.xml
|
||||
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config {project-root}/_bmad/cis/workflows/design-thinking/workflow.yaml
|
||||
3. Pass the yaml path _bmad/cis/workflows/design-thinking/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
|
||||
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
|
||||
5. Save outputs after EACH section when generating any documents from templates
|
||||
</steps>
|
||||
**Goal:** Guide human-centered design through empathy, definition, ideation, prototyping, and testing.
|
||||
|
||||
**Your Role:** You are a human-centered design facilitator. Keep users at the center, defer judgment during ideation, prototype quickly, and never give time estimates.
|
||||
|
||||
## Conventions
|
||||
|
||||
- Bare paths (e.g. `template.md`) resolve from the skill root.
|
||||
- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).
|
||||
- `{project-root}`-prefixed paths resolve from the project working directory.
|
||||
- `{skill-name}` resolves to the skill directory's basename.
|
||||
|
||||
## On Activation
|
||||
|
||||
### Step 1: Resolve the Workflow Block
|
||||
|
||||
Run: `python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`
|
||||
|
||||
**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:
|
||||
|
||||
1. `{skill-root}/customize.toml` — defaults
|
||||
2. `{project-root}/_bmad/custom/{skill-name}.toml` — team overrides
|
||||
3. `{project-root}/_bmad/custom/{skill-name}.user.toml` — personal overrides
|
||||
|
||||
Any 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.
|
||||
|
||||
### Step 2: Execute Prepend Steps
|
||||
|
||||
Execute each entry in `{workflow.activation_steps_prepend}` in order before proceeding.
|
||||
|
||||
### Step 3: Load Persistent Facts
|
||||
|
||||
Treat 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.
|
||||
|
||||
### Step 4: Load Config
|
||||
|
||||
Load config from `{project-root}/_bmad/cis/config.yaml` and resolve:
|
||||
|
||||
- `output_folder`
|
||||
- `user_name`
|
||||
- `communication_language`
|
||||
- `date` as the system-generated current datetime
|
||||
|
||||
### Step 5: Greet the User
|
||||
|
||||
Greet `{user_name}`, speaking in `{communication_language}`.
|
||||
|
||||
### Step 6: Execute Append Steps
|
||||
|
||||
Execute each entry in `{workflow.activation_steps_append}` in order.
|
||||
|
||||
Activation is complete. Begin the workflow below.
|
||||
|
||||
## Paths
|
||||
|
||||
- `template_file` = `./template.md`
|
||||
- `design_methods_file` = `./design-methods.csv`
|
||||
- `default_output_file` = `{output_folder}/design-thinking-{date}.md`
|
||||
|
||||
## Inputs
|
||||
|
||||
- If the caller provides context via the data attribute, load it before workflow Step 1 and use it to ground the session.
|
||||
- Load and understand the full contents of `{design_methods_file}` before workflow 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.
|
||||
|
||||
## Facilitation Principles
|
||||
|
||||
- Keep users at the center of every decision.
|
||||
- Encourage divergent thinking before convergent action.
|
||||
- Make ideas tangible quickly; prototypes beat discussion.
|
||||
- Treat failure as feedback.
|
||||
- Test with real users rather than assumptions.
|
||||
- Balance empathy with momentum.
|
||||
|
||||
## Execution
|
||||
|
||||
<workflow>
|
||||
|
||||
<step n="1" goal="Gather context and define design challenge">
|
||||
Ask the user about their design challenge:
|
||||
|
||||
- What problem or opportunity are you exploring?
|
||||
- Who are the primary users or stakeholders?
|
||||
- What constraints exist (time, budget, technology)?
|
||||
- What does success look like for this project?
|
||||
- What existing research or context should we consider?
|
||||
|
||||
Load any context data provided via the data attribute.
|
||||
|
||||
Create a clear design challenge statement.
|
||||
|
||||
<template-output>design_challenge</template-output>
|
||||
<template-output>challenge_statement</template-output>
|
||||
</step>
|
||||
|
||||
<step n="2" goal="EMPATHIZE - Build understanding of users">
|
||||
Guide the user through empathy-building activities. Explain in your own voice why deep empathy with users is essential before jumping to solutions.
|
||||
|
||||
Review empathy methods from `{design_methods_file}` for the `empathize` phase and select 3-5 methods that fit the design challenge context. Consider:
|
||||
|
||||
- Available resources and access to users
|
||||
- Time constraints
|
||||
- Type of product or service being designed
|
||||
- Depth of understanding needed
|
||||
|
||||
Offer the selected methods with guidance on when each works best, then ask which methods the user has used or can use, or make a recommendation based on the specific challenge.
|
||||
|
||||
Help gather and synthesize user insights:
|
||||
|
||||
- What did users say, think, do, and feel?
|
||||
- What pain points emerged?
|
||||
- What surprised you?
|
||||
- What patterns do you see?
|
||||
|
||||
<template-output>user_insights</template-output>
|
||||
<template-output>key_observations</template-output>
|
||||
<template-output>empathy_map</template-output>
|
||||
</step>
|
||||
|
||||
<step n="3" goal="DEFINE - Frame the problem clearly">
|
||||
<energy-checkpoint>
|
||||
Check in: "We've gathered rich user insights. How are you feeling? Ready to synthesize them into problem statements?"
|
||||
</energy-checkpoint>
|
||||
|
||||
Transform observations into actionable problem statements.
|
||||
|
||||
Guide the user through problem framing:
|
||||
|
||||
1. Create a Point of View statement: "[User type] needs [need] because [insight]"
|
||||
2. Generate "How Might We" questions that open solution space
|
||||
3. Identify key insights and opportunity areas
|
||||
|
||||
Ask probing questions:
|
||||
|
||||
- What's the real problem we're solving?
|
||||
- Why does this matter to users?
|
||||
- What would success look like for them?
|
||||
- What assumptions are we making?
|
||||
|
||||
<template-output>pov_statement</template-output>
|
||||
<template-output>hmw_questions</template-output>
|
||||
<template-output>problem_insights</template-output>
|
||||
</step>
|
||||
|
||||
<step n="4" goal="IDEATE - Generate diverse solutions">
|
||||
Facilitate creative solution generation. Explain in your own voice the importance of divergent thinking and deferring judgment during ideation.
|
||||
|
||||
Review ideation methods from `{design_methods_file}` for the `ideate` phase and select 3-5 methods that fit the context. Consider:
|
||||
|
||||
- Group versus individual ideation
|
||||
- Time available
|
||||
- Problem complexity
|
||||
- Team creativity comfort level
|
||||
|
||||
Offer the selected methods with brief descriptions of when each works best.
|
||||
|
||||
Walk through the chosen method or methods:
|
||||
|
||||
- Generate at least 15-30 ideas
|
||||
- Build on others' ideas
|
||||
- Go for wild and practical
|
||||
- Defer judgment
|
||||
|
||||
Help cluster and select top concepts:
|
||||
|
||||
- Which ideas excite you most?
|
||||
- Which ideas address the core user need?
|
||||
- Which ideas are feasible given the constraints?
|
||||
- Select 2-3 ideas to prototype
|
||||
|
||||
<template-output>ideation_methods</template-output>
|
||||
<template-output>generated_ideas</template-output>
|
||||
<template-output>top_concepts</template-output>
|
||||
</step>
|
||||
|
||||
<step n="5" goal="PROTOTYPE - Make ideas tangible">
|
||||
<energy-checkpoint>
|
||||
Check in: "We've generated lots of ideas. How is your energy for making some of them tangible through prototyping?"
|
||||
</energy-checkpoint>
|
||||
|
||||
Guide creation of low-fidelity prototypes for testing. Explain in your own voice why rough and quick prototypes are better than polished ones at this stage.
|
||||
|
||||
Review prototyping methods from `{design_methods_file}` for the `prototype` phase and select 2-4 methods that fit the solution type. Consider:
|
||||
|
||||
- Physical versus digital product
|
||||
- Service versus product
|
||||
- Available materials and tools
|
||||
- What needs to be tested
|
||||
|
||||
Offer the selected methods with guidance on fit.
|
||||
|
||||
Help define the prototype:
|
||||
|
||||
- What's the minimum needed to test your assumptions?
|
||||
- What are you trying to learn?
|
||||
- What should users be able to do?
|
||||
- What can you fake versus build?
|
||||
|
||||
<template-output>prototype_approach</template-output>
|
||||
<template-output>prototype_description</template-output>
|
||||
<template-output>features_to_test</template-output>
|
||||
</step>
|
||||
|
||||
<step n="6" goal="TEST - Validate with users">
|
||||
Design the validation approach and capture learnings. Explain in your own voice why observing what users do matters more than what they say.
|
||||
|
||||
Help plan testing:
|
||||
|
||||
- Who will you test with? Aim for 5-7 users.
|
||||
- What tasks will they attempt?
|
||||
- What questions will you ask?
|
||||
- How will you capture feedback?
|
||||
|
||||
Guide feedback collection:
|
||||
|
||||
- What worked well?
|
||||
- Where did they struggle?
|
||||
- What surprised them, and you?
|
||||
- What questions arose?
|
||||
- What would they change?
|
||||
|
||||
Synthesize learnings:
|
||||
|
||||
- What assumptions were validated or invalidated?
|
||||
- What needs to change?
|
||||
- What should stay?
|
||||
- What new insights emerged?
|
||||
|
||||
<template-output>testing_plan</template-output>
|
||||
<template-output>user_feedback</template-output>
|
||||
<template-output>key_learnings</template-output>
|
||||
</step>
|
||||
|
||||
<step n="7" goal="Plan next iteration">
|
||||
<energy-checkpoint>
|
||||
Check in: "Great work. How is your energy for final planning and defining next steps?"
|
||||
</energy-checkpoint>
|
||||
|
||||
Define clear next steps and success criteria.
|
||||
|
||||
Based on testing insights:
|
||||
|
||||
- What refinements are needed?
|
||||
- What's the priority action?
|
||||
- Who needs to be involved?
|
||||
- What sequence makes sense?
|
||||
- How will you measure success?
|
||||
|
||||
Determine the next cycle:
|
||||
|
||||
- Do you need more empathy work?
|
||||
- Should you reframe the problem?
|
||||
- Are you ready to refine the prototype?
|
||||
- Is it time to pilot with real users?
|
||||
|
||||
<template-output>refinements</template-output>
|
||||
<template-output>action_items</template-output>
|
||||
<template-output>success_metrics</template-output>
|
||||
|
||||
<action>Run: `python3 {project-root}/_bmad/scripts/resolve_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.</action>
|
||||
</step>
|
||||
|
||||
</workflow>
|
||||
|
||||
@@ -0,0 +1,41 @@
|
||||
# DO NOT EDIT -- overwritten on every update.
|
||||
#
|
||||
# Workflow customization surface for bmad-cis-design-thinking. Mirrors the
|
||||
# agent customization shape under the [workflow] namespace.
|
||||
|
||||
[workflow]
|
||||
|
||||
# --- Configurable below. Overrides merge per BMad structural rules: ---
|
||||
# scalars: override wins • arrays (persistent_facts, activation_steps_*): append
|
||||
# arrays-of-tables with `code`/`id`: replace matching items, append new ones.
|
||||
|
||||
# Steps to run before the standard activation (config load, greet).
|
||||
# Overrides append. Use for pre-flight loads, compliance checks, etc.
|
||||
|
||||
activation_steps_prepend = []
|
||||
|
||||
# Steps to run after greet but before the workflow begins.
|
||||
# Overrides append. Use for context-heavy setup that should happen
|
||||
# once the user has been acknowledged.
|
||||
|
||||
activation_steps_append = []
|
||||
|
||||
# Persistent facts the workflow keeps in mind for the whole run
|
||||
# (standards, compliance constraints, stylistic guardrails).
|
||||
# Distinct from the runtime memory sidecar — these are static context
|
||||
# loaded on activation. Overrides append.
|
||||
#
|
||||
# Each entry is either:
|
||||
# - a literal sentence, e.g. "Empathy interviews must include at least 5 real users before ideation."
|
||||
# - a file reference prefixed with `file:`, e.g. "file:{project-root}/docs/standards.md"
|
||||
# (glob patterns are supported; the file's contents are loaded and treated as facts).
|
||||
|
||||
persistent_facts = [
|
||||
"file:{project-root}/**/project-context.md",
|
||||
]
|
||||
|
||||
# Scalar: executed when the workflow reaches Step 7 (Plan next iteration),
|
||||
# after refinements, action items, and success metrics are captured. Override wins.
|
||||
# Leave empty for no custom post-completion behavior.
|
||||
|
||||
on_complete = ""
|
||||
@@ -0,0 +1,31 @@
|
||||
phase,method_name,description,facilitation_prompts
|
||||
empathize,User Interviews,Conduct deep conversations to understand user needs experiences and pain points through active listening,What brings you here today?|Walk me through a recent experience|What frustrates you most?|What would make this easier?|Tell me more about that
|
||||
empathize,Empathy Mapping,Create visual representation of what users say think do and feel to build deep understanding,What did they say?|What might they be thinking?|What actions did they take?|What emotions surfaced?
|
||||
empathize,Shadowing,Observe users in their natural environment to see unspoken behaviors and contextual factors,Watch without interrupting|Note their workarounds|What patterns emerge?|What do they not say?
|
||||
empathize,Journey Mapping,Document complete user experience across touchpoints to identify pain points and opportunities,What's their starting point?|What steps do they take?|Where do they struggle?|What delights them?|What's the emotional arc?
|
||||
empathize,Diary Studies,Have users document experiences over time to capture authentic moments and evolving needs,What did you experience today?|How did you feel?|What worked or didn't?|What surprised you?
|
||||
define,Problem Framing,Transform observations into clear actionable problem statements that inspire solution generation,What's the real problem?|Who experiences this?|Why does it matter?|What would success look like?
|
||||
define,How Might We,Reframe problems as opportunity questions that open solution space without prescribing answers,How might we help users...?|How might we make it easier to...?|How might we reduce the friction of...?
|
||||
define,Point of View Statement,Create specific user-centered problem statements that capture who what and why,User type needs what because insight|What's driving this need?|Why does it matter to them?
|
||||
define,Affinity Clustering,Group related observations and insights to reveal patterns and opportunity themes,What connects these?|What themes emerge?|Group similar items|Name each cluster|What story do they tell?
|
||||
define,Jobs to be Done,Identify functional emotional and social jobs users are hiring solutions to accomplish,What job are they trying to do?|What progress do they want?|What are they really hiring this for?|What alternatives exist?
|
||||
ideate,Brainstorming,Generate large quantity of diverse ideas without judgment to explore solution space fully,No bad ideas|Build on others|Go for quantity|Be visual|Stay on topic|Defer judgment
|
||||
ideate,Crazy 8s,Rapidly sketch eight solution variations in eight minutes to force quick creative thinking,Fold paper in 8|1 minute per sketch|No overthinking|Quantity over quality|Push past obvious
|
||||
ideate,SCAMPER Design,Apply seven design lenses to existing solutions - Substitute Combine Adapt Modify Purposes Eliminate Reverse,What could we substitute?|How could we combine elements?|What could we adapt?|How could we modify it?|Other purposes?|What to eliminate?|What if reversed?
|
||||
ideate,Provotype Sketching,Create deliberately provocative or extreme prototypes to spark breakthrough thinking,What's the most extreme version?|Make it ridiculous|Push boundaries|What useful insights emerge?
|
||||
ideate,Analogous Inspiration,Find inspiration from completely different domains to spark innovative connections,What other field solves this?|How does nature handle this?|What's an analogous problem?|What can we borrow?
|
||||
prototype,Paper Prototyping,Create quick low-fidelity sketches and mockups to make ideas tangible for testing,Sketch it out|Make it rough|Focus on core concept|Test assumptions|Learn fast
|
||||
prototype,Role Playing,Act out user scenarios and service interactions to test experience flow and pain points,Play the user|Act out the scenario|What feels awkward?|Where does it break?|What works?
|
||||
prototype,Wizard of Oz,Simulate complex functionality manually behind scenes to test concept before building,Fake the backend|Focus on experience|What do they think is happening?|Does the concept work?
|
||||
prototype,Storyboarding,Visualize user experience across time and touchpoints as sequential illustrated narrative,What's scene 1?|How does it progress?|What's the emotional journey?|Where's the climax?|How does it resolve?
|
||||
prototype,Physical Mockups,Build tangible artifacts users can touch and interact with to test form and function,Make it 3D|Use basic materials|Make it interactive|Test ergonomics|Gather reactions
|
||||
test,Usability Testing,Watch users attempt tasks with prototype to identify friction points and opportunities,Try to accomplish X|Think aloud please|Don't help them|Where do they struggle?|What surprises them?
|
||||
test,Feedback Capture Grid,Organize user feedback across likes questions ideas and changes for actionable insights,What did they like?|What questions arose?|What ideas did they have?|What needs changing?
|
||||
test,A/B Testing,Compare two variations to understand which approach better serves user needs,Show version A|Show version B|Which works better?|Why the difference?|What does data show?
|
||||
test,Assumption Testing,Identify and validate critical assumptions underlying your solution to reduce risk,What are we assuming?|How can we test this?|What would prove us wrong?|What's the riskiest assumption?
|
||||
test,Iterate and Refine,Use test insights to improve prototype through rapid cycles of refinement and re-testing,What did we learn?|What needs fixing?|What stays?|Make changes quickly|Test again
|
||||
implement,Pilot Programs,Launch small-scale real-world implementation to learn before full rollout,Start small|Real users|Real context|What breaks?|What works?|Scale lessons learned
|
||||
implement,Service Blueprinting,Map all service components interactions and touchpoints to guide implementation,What's visible to users?|What happens backstage?|What systems are needed?|Where are handoffs?
|
||||
implement,Design System Creation,Build consistent patterns components and guidelines for scalable implementation,What patterns repeat?|Create reusable components|Document standards|Enable consistency
|
||||
implement,Stakeholder Alignment,Bring team and stakeholders along journey to build shared understanding and commitment,Show the research|Walk through prototypes|Share user stories|Build empathy|Get buy-in
|
||||
implement,Measurement Framework,Define success metrics and feedback loops to track impact and inform future iterations,How will we measure success?|What are key metrics?|How do we gather feedback?|When do we revisit?
|
||||
|
@@ -0,0 +1,111 @@
|
||||
# Design Thinking Session: {{project_name}}
|
||||
|
||||
**Date:** {{date}}
|
||||
**Facilitator:** {{user_name}}
|
||||
**Design Challenge:** {{design_challenge}}
|
||||
|
||||
---
|
||||
|
||||
## 🎯 Design Challenge
|
||||
|
||||
{{challenge_statement}}
|
||||
|
||||
---
|
||||
|
||||
## 👥 EMPATHIZE: Understanding Users
|
||||
|
||||
### User Insights
|
||||
|
||||
{{user_insights}}
|
||||
|
||||
### Key Observations
|
||||
|
||||
{{key_observations}}
|
||||
|
||||
### Empathy Map Summary
|
||||
|
||||
{{empathy_map}}
|
||||
|
||||
---
|
||||
|
||||
## 🎨 DEFINE: Frame the Problem
|
||||
|
||||
### Point of View Statement
|
||||
|
||||
{{pov_statement}}
|
||||
|
||||
### How Might We Questions
|
||||
|
||||
{{hmw_questions}}
|
||||
|
||||
### Key Insights
|
||||
|
||||
{{problem_insights}}
|
||||
|
||||
---
|
||||
|
||||
## 💡 IDEATE: Generate Solutions
|
||||
|
||||
### Selected Methods
|
||||
|
||||
{{ideation_methods}}
|
||||
|
||||
### Generated Ideas
|
||||
|
||||
{{generated_ideas}}
|
||||
|
||||
### Top Concepts
|
||||
|
||||
{{top_concepts}}
|
||||
|
||||
---
|
||||
|
||||
## 🛠️ PROTOTYPE: Make Ideas Tangible
|
||||
|
||||
### Prototype Approach
|
||||
|
||||
{{prototype_approach}}
|
||||
|
||||
### Prototype Description
|
||||
|
||||
{{prototype_description}}
|
||||
|
||||
### Key Features to Test
|
||||
|
||||
{{features_to_test}}
|
||||
|
||||
---
|
||||
|
||||
## ✅ TEST: Validate with Users
|
||||
|
||||
### Testing Plan
|
||||
|
||||
{{testing_plan}}
|
||||
|
||||
### User Feedback
|
||||
|
||||
{{user_feedback}}
|
||||
|
||||
### Key Learnings
|
||||
|
||||
{{key_learnings}}
|
||||
|
||||
---
|
||||
|
||||
## 🚀 Next Steps
|
||||
|
||||
### Refinements Needed
|
||||
|
||||
{{refinements}}
|
||||
|
||||
### Action Items
|
||||
|
||||
{{action_items}}
|
||||
|
||||
### Success Metrics
|
||||
|
||||
{{success_metrics}}
|
||||
|
||||
---
|
||||
|
||||
_Generated using BMAD Creative Intelligence Suite - Design Thinking Workflow_
|
||||
Reference in New Issue
Block a user