pdca-plan

Guides the Plan phase of a PDCA cycle with problem definition, SMART objectives, and improvement hypotheses.

1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/NestorMonroy/thyrox --skill pdca-plan-nestormonroy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pdca-plan
Source: https://github.com/NestorMonroy/thyrox/tree/main/.claude/skills/pdca-plan
Command: npx skills add https://github.com/NestorMonroy/thyrox --skill pdca-plan-nestormonroy

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 step 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. - Hypothesis Formulation: Produces a verifiable improvement hypothesis in the format "If [action], then [result], because [mechanism]". - Root Cause Techniques: Includes step-by-step guides for 5 Whys, Fishbone/Ishikawa, Pareto 80/20, IS/IS NOT, and 5W2H. - Use Case: An API's p95 latency exceeds 2s on 30% of requests. Use this Skill to document the baseline, set a target of under 800ms by a fixed date, and formulate the hypothesis that a composite index will resolve the full table scan. ## Quick Start Ask the assistant to start a PDCA Plan for your problem, providing the current metric, its baseline value, and the impact it has on your business.

Frequently Asked Questions about pdca-plan

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

FAQPage Schema
How do I write a good problem statement for a PDCA cycle?▼

A good problem statement describes the observable symptom with data, such as "API p95 latency exceeds 2s on 30% of requests since 2026-03-01". Use the IS/IS NOT technique to delimit what, where, when, and magnitude, and avoid stating assumed causes or implied solutions.

What is a SMART objective in continuous improvement?▼

A SMART objective is Specific, Measurable, Achievable, Relevant, and Time-bound. For example: reduce p95 latency of the /orders endpoint from 2.1s to under 800ms by 2026-05-01 without degrading p99. It must include a numeric baseline and target.

When should I use PDCA versus DMAIC?▼

Use PDCA for iterative improvement cycles with a single testable hypothesis per cycle. Choose DMAIC when the problem requires deep statistical analysis of variability, as it offers more robust tools for complex data-driven investigations.

Which root cause analysis technique should I use?▼

Use 5 Whys for clear symptoms with linear causal chains, Fishbone/Ishikawa when multiple cause categories exist, Pareto 80/20 to prioritize among many defect types, and IS/IS NOT when the problem is diffuse or the team disagrees on its definition.

Can I test multiple hypotheses in one PDCA cycle?▼

No. Each PDCA cycle tests exactly one hypothesis, because changing two variables at once makes it impossible to attribute the observed effect. Additional hypotheses go to the backlog for subsequent cycles.

What are the limitations of the PDCA Plan step?▼

The Plan step guides the planning process but does not replace domain expert 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.