bmad-cis-problem-solving

Invoke the workflow by asking to be guided through structured problem solving. The assistant walks you through eight steps: problem definition, boundary diagnosis, root cause analysis, force field analysis, solution generation, evaluation, implementation planning, and monitoring setup.

The workflow references a solving-methods CSV covering diagnosis methods including Five Whys for linear cause chains, Fishbone Diagrams for multi-factor problems, and Systems Thinking for interconnected dynamics. It selects 2-3 methods matched to your problem type.

It generates a Markdown report saved to a dated file in the configured output folder. The report follows a template covering problem definition, root cause analysis, solution evaluation, implementation plan, success metrics, validation plan, and lessons learned.

Yes, customization is handled through TOML files. A base customize.toml in the skill directory defines defaults, and team or user override files under the project's _bmad/custom directory can append activation steps, persistent facts, and completion actions.

Avoid it for simple, well-understood issues with known fixes, where the multi-step diagnosis adds overhead without value. It is designed for complex or recurring problems where symptoms have resisted previous solution attempts.