bmad-cis-design-thinking

Start by saying "let's run design thinking" and describe your challenge. The facilitator guides you through seven steps: context gathering, empathy, problem definition, ideation, prototyping, testing, and iteration planning, saving output after each step.

The workflow loads methods from a design-methods.csv file organized by phase (empathize, define, ideate, prototype, test). It recommends 3-5 methods per phase based on your resources, constraints, and challenge type.

Each session generates a Markdown report saved to your configured output folder. It includes the challenge statement, empathy map, POV statement, How Might We questions, generated ideas, prototype description, user feedback, and action items.

Yes, customization uses TOML files with base, team, and user override layers. You can add activation steps, persistent facts, and an on-complete action without editing the core skill files.

Design thinking fits open-ended, user-centered problems with ambiguity. It is less suitable for purely technical issues with known solutions, compliance-driven tasks, or situations where requirements are already fully specified.