bmad-cis-problem-solving

Invoke the skill by asking to be guided through structured problem solving. The workflow then walks you through nine steps: problem definition, boundary diagnosis, root cause analysis, force field analysis, solution generation, evaluation, implementation planning, and validation metrics.

It references a solving-methods CSV covering diagnosis methods like Five Whys, Fishbone Diagrams, and Is/Is Not Analysis, plus synthesis methods like TRIZ, Lateral Thinking, and Morphological Analysis, and evaluation tools like Decision Matrices and Cost Benefit Analysis.

It generates a Markdown report saved to the configured output folder, following the bundled template. The report covers the refined problem statement, root cause analysis, generated and evaluated solutions, an implementation plan, success metrics, and optional lessons learned.

Yes. A customize.toml file supports prepended or appended activation steps, persistent facts loaded from files or globs, and an on_complete hook. Team and user-level TOML overrides merge with the defaults using BMad structural merge rules.

It is a poor fit for trivial issues with obvious fixes or emergencies needing immediate action, since the full nine-step diagnosis and evaluation process is deliberately thorough. It works best for complex, recurring, or multi-factor problems.