bmad-cis-design-thinking

Invoke the skill by saying you want to run design thinking, then answer guided questions through five phases: empathize, define, ideate, prototype, and test. The facilitator selects methods from a design methods catalog and saves a structured session document after each step.

The session generates a Markdown document from a template containing the design challenge statement, user insights, empathy map, POV statement, How Might We questions, generated ideas, prototype description, testing plan, and next-step action items.

Yes, customization works through TOML override files at team and user level. You can add activation steps, persistent facts, and an on-complete action; scalars override defaults while arrays append following structural merge rules.

The workflow targets 15-30 ideas during ideation, encouraging wild and practical options while deferring judgment. Afterward, ideas are clustered and 2-3 top concepts are selected for prototyping.

Design thinking fits open-ended user problems needing empathy and exploration. It is less suitable for purely technical implementation tasks, well-defined requirements, or situations where solutions are already validated and only execution remains.