bmad-cis-problem-solving

Guide users through diagnostic, analytical, and implementation phases for complex problems.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a structured, repeatable framework for diagnosing complex problems, identifying root causes, and generating actionable solutions, preventing the common pitfall of jumping to premature conclusions.

Core Features & Use Cases

  • Systematic Diagnosis: Uses proven methodologies like Is/Is Not analysis and Force Field analysis to bound problems and identify constraints.
  • Root Cause Analysis: Guides users through deep-dive techniques like the Five Whys and Fishbone diagrams to distinguish symptoms from underlying causes.
  • Use Case: Use this when facing a recurring technical or organizational bottleneck where the root cause is unclear and you need a guided, rigorous approach to develop a sustainable fix.

Quick Start

Activate the bmad-cis-problem-solving skill to guide me through structured problem solving for my current project challenge.

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 identify the root cause of a recurring technical bottleneck?

Systematic root cause identification uses Is/Is Not analysis and Five Whys methodologies to distinguish symptoms from underlying causes, preventing premature conclusions when diagnosing recurring technical or organizational bottlenecks.

What is the best way to structure decision-making for complex organizational challenges?

Structured decision-making for complex challenges uses customizable workflow templates and persistent context management to apply analytical methodologies like Force Field analysis, bounding problems to generate rigorous, evidence-based solutions.

Can I use this guided problem-solving approach for unclear project constraints?

Yes, this guided approach suits unclear project constraints by applying systematic diagnosis through Is/Is Not and Force Field analysis to bound complex technical or organizational challenges and identify specific constraints.

How do I start a structured problem-solving workflow for my current project?

You start a structured problem-solving workflow by activating the skill to guide you through diagnostic, analytical, and implementation phases using customizable workflow templates and persistent context management for your current project challenge.

When should I avoid jumping to conclusions during problem diagnosis?

You should avoid jumping to conclusions during problem diagnosis when facing complex technical or organizational challenges where the root cause is unclear, relying instead on systematic frameworks to ensure rigorous, evidence-based solution generation.