pdca-act

Decides whether to standardize or restart a PDCA improvement cycle based on Check results.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? After running a PDCA improvement pilot, teams often fail to close the loop: successful changes regress because they were never standardized, and failed cycles repeat because lessons were never documented. This Skill guides the Act phase of the PDCA cycle so every improvement ends with a clear, documented decision. ## Core Features & Use Cases - Decision tree for Act: Classifies Check results (success, partial, failure, regression) and maps each to a concrete action: standardize and scale, adjust first, or start a new cycle with a refined hypothesis. - Standardization toolkit: Covers SOP updates, poka-yoke error-proofing, Yokoten horizontal deployment to analogous processes, rollout planning, stakeholder communication, and new baseline definition. - Lessons learned and A3 Report: Captures learnings across process, technique, hypothesis, data, and communication dimensions, with an optional one-page A3 Report template for formal stakeholder communication. - Use Case: A team reduced API latency in a pilot service. Use this Skill to decide whether to standardize the fix, write the new SOP with poka-yoke safeguards, plan the rollout to remaining services, and notify analogous teams via Yokoten. ## Quick Start Ask the assistant to run the pdca-act step for your work package using the completed pdca-check.md to decide whether to standardize or start a new cycle.

Frequently Asked Questions about pdca-act

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

FAQPage Schema
How do I decide whether to standardize or repeat a PDCA cycle?▼

Base the decision on the Check verdict. If the objective was met without regressions in control metrics, standardize and scale. If improvement was partial or the hypothesis was wrong, start a new cycle with an adjusted hypothesis or implementation plan.

What is Yokoten in Lean continuous improvement?▼

Yokoten is the Lean principle of horizontal deployment: propagating lessons from one improvement to analogous processes. It follows four steps: identify similar processes, adapt the solution to local context, transfer the learning, and verify adoption.

What is poka-yoke and when should I apply it?▼

Poka-yoke is error-proofing applied before scaling a standardized change. Use system constraints, automation, regression alerts, or prominent documentation to prevent anyone from accidentally reverting the improvement.

What is the difference between PDCA and SDCA cycles?▼

PDCA improves a process by establishing a new standard, while SDCA (Standardize-Do-Check-Act) maintains an existing standard. When SDCA detects a systematic deviation, it triggers a new PDCA cycle.

When should I not run the PDCA Act step?▼

Do not run Act without a completed Check containing a clear data-backed verdict. If Check identified external contamination that invalidates the pilot data, repeat the Do phase first instead of deciding.

What is an A3 Report used for in PDCA?▼

An A3 Report summarizes the full PDCA cycle on one page: context, current situation, objective, root cause analysis, countermeasures, results, and next steps. It is useful for formal communication with stakeholders who did not participate in the cycle.