bmad-cis-problem-solving

Guide users through diagnosis, root cause analysis, and implementation planning.

Updated Jul 11, 2026
One-click install
npx skills add https://github.com/marcmontecalvo/kinward --skill bmad-cis-problem-solving-marcmontecalvo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-cis-problem-solving
Source: https://github.com/marcmontecalvo/kinward/tree/main/.agents/skills/bmad-cis-problem-solving
Command: npx skills add https://github.com/marcmontecalvo/kinward --skill bmad-cis-problem-solving-marcmontecalvo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill addresses the tendency to jump to premature solutions by providing a rigorous, step-by-step framework for diagnosing root causes and planning effective, validated interventions.

Core Features & Use Cases

  • Systematic Diagnosis: Uses structured methods like Is/Is Not analysis and Five Whys to uncover the true nature of a problem.
  • Strategic Planning: Guides the user through force field analysis, solution generation, and implementation planning to ensure actions are both feasible and impactful.
  • Use Case: Use this when facing a recurring operational bottleneck or a complex project hurdle where the underlying cause is unclear and requires a disciplined, analytical approach to resolve.

Quick Start

Activate the bmad-cis-problem-solving skill to begin a guided session for diagnosing the current project bottleneck.

Frequently Asked Questions about bmad-cis-problem-solving

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the root cause of a complex operational bottleneck?

To find the root cause of an operational bottleneck, this skill applies structured diagnosis methods like Is/Is Not analysis and Five Whys to uncover the true underlying nature of the problem before planning interventions.

What is the best way to plan interventions for unclear project hurdles?

The best way to plan interventions for unclear project hurdles is using force field analysis and solution generation to ensure the actions you implement are both feasible and impactful for the specific challenge.

How do I stop my team from jumping to premature solutions during decision-making?

To stop jumping to premature solutions during decision-making, use a rigorous, step-by-step framework that requires evidence-based problem resolution and objective evaluation before any implementation planning begins.

When should I use systems thinking for problem-solving over standard troubleshooting?

You should use systems thinking for problem-solving when facing recurring operational bottlenecks or complex strategic challenges that require a disciplined, analytical, and documented approach to resolve effectively.

Can I use this structured problem-solving approach for technical and strategic challenges?

Yes, you can use this structured problem-solving approach for technical and strategic challenges, as it applies systems thinking to guide objective evaluation and repeatable, documented workflows across complex operational scenarios.

What are the limitations of using root cause analysis for recurring bottlenecks?

A limitation of using root cause analysis for recurring bottlenecks is that it requires a disciplined, analytical approach; it may not suit simple, isolated incidents where the underlying cause is already immediately obvious.