pdca-plan

Guides the Plan phase of a PDCA cycle to define problems, baselines, SMART objectives, and improvement hypotheses.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/jcg-admin/IACT-ui --skill pdca-plan-jcg-admin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pdca-plan
Source: https://github.com/jcg-admin/IACT-ui/tree/main/.claude/skills/pdca-plan
Command: npx skills add https://github.com/jcg-admin/IACT-ui --skill pdca-plan-jcg-admin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Teams often jump to solutions without defining the problem, establishing a measurable baseline, or formulating a testable hypothesis, making improvement efforts impossible to verify. This Skill structures the Plan phase of the PDCA cycle so every improvement starts with data and a clear objective. ## Core Features & Use Cases - Problem Definition with IS/IS NOT: Delimits the problem across what, where, when, and magnitude dimensions to avoid assumed causes. - SMART Objective Builder: Guides creation of specific, measurable, achievable, relevant, and time-bound objectives with baseline and target values. - Root Cause Techniques: Includes step-by-step guides for 5 Whys, Fishbone/Ishikawa, Pareto 80/20, IS/IS NOT, and 5W2H analysis. - Use Case: When an API's p95 latency exceeds target, use this Skill to produce a pdca-plan.md artifact containing the problem statement, baseline metrics, a SMART objective, a causal hypothesis, and an action plan ready for the Do phase. ## Quick Start Ask the assistant to start a PDCA Plan cycle for your current problem, providing the observable symptom and any available metrics.

Frequently Asked Questions about pdca-plan

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

FAQPage Schema
How do I start a PDCA Plan cycle for a recurring problem?▼

Begin by defining the problem with the IS/IS NOT technique across what, where, when, and magnitude dimensions, using observable data rather than assumed causes. Then establish a numeric baseline, set a SMART objective, and formulate one testable hypothesis before moving to the Do phase.

What root cause analysis techniques does the PDCA Plan phase use?▼

The Plan phase supports 5 Whys for linear causal chains, Fishbone/Ishikawa diagrams for multi-category brainstorming, Pareto 80/20 for prioritizing vital causes, IS/IS NOT for problem delimitation, and 5W2H for full context. Step-by-step guides are included in the references.

When should I use DMAIC instead of a PDCA cycle?▼

Use DMAIC when the problem involves complex statistical variability requiring deeper analytical tools. PDCA Plan is better suited for iterative improvement cycles where a single hypothesis can be tested quickly with available data.

What makes a SMART objective valid in a PDCA plan?▼

A valid SMART objective names one exact metric, includes numeric baseline and target values, is achievable by the team, connects to business impact, and has a deadline. Objectives combining two metrics should designate a primary goal and list others as constraints.

Why should a PDCA cycle test only one hypothesis at a time?▼

Testing multiple hypotheses simultaneously makes it impossible to determine which change caused the observed result during the Check phase. Each cycle should isolate one variable, with additional hypotheses queued for subsequent cycles.

What are the limitations of the PDCA Plan skill?▼

The skill guides the planning process but does not replace domain expertise or judgment. If no historical data exists, the first Plan iteration may only define how to collect data, and statistically complex problems may require DMAIC instead.