bmad-cis-design-thinking

Invoke the workflow by saying you want to run design thinking, then answer the facilitator's questions across seven steps. The session produces a Markdown document covering empathy insights, problem framing, ideas, prototype plans, and test learnings.

The session writes a Markdown file to the configured output folder containing the challenge statement, empathy map, POV statement, How-Might-We questions, generated ideas, prototype description, testing plan, and action items, saved incrementally after each step.

Yes, customization is handled through TOML files. Team overrides go in _bmad/custom/bmad-cis-design-thinking.toml and personal overrides in a .user.toml variant, supporting prepended steps, appended steps, and persistent facts.

The facilitator loads a design-methods.csv catalog and selects 3-5 methods per phase (empathize, ideate, prototype) based on your context, such as available user access, time constraints, and whether the product is physical or digital.

Skip it for well-understood problems with validated requirements or minor incremental changes. The full empathy-to-test cycle is designed for open-ended challenges where user needs and problem framing are still uncertain.