bmad-cis-problem-solving

Invoke the skill and describe your challenge; it guides you through nine steps covering problem definition, Is/Is Not boundary analysis, root cause analysis, solution generation, evaluation, and implementation planning. Each step saves progress to a Markdown report.

It supports Five Whys for linear cause chains, Fishbone Diagrams for multi-factor problems, and Systems Thinking for interconnected dynamics. Methods are loaded from a solving-methods CSV and selected based on your problem type.

Yes, the customize.toml file lets you add activation steps, persistent facts, and an on-complete action. Team and user-level TOML overrides merge with defaults using structural merge rules.

It produces a Markdown report saved to the configured output folder, containing the refined problem statement, root cause analysis, force field analysis, evaluated solutions, implementation plan, success metrics, and lessons learned.

Avoid it for simple, well-understood issues with known fixes, where a full nine-step diagnosis adds overhead without value. It is designed for complex, ambiguous, or recurring problems where root causes are unclear.