pdca-act

Decides whether to standardize or adjust a PDCA improvement and documents lessons learned.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? After running a PDCA improvement cycle, teams often fail to close the loop: successful pilots regress because they were never standardized, and failed cycles repeat because lessons were never captured. This Skill guides the Act step of the PDCA cycle so every improvement ends with a clear, documented decision. ## Core Features & Use Cases - Decision tree for Act: Routes the Check verdict (success, partial, failure) to standardize-and-scale or to a new adjusted cycle, with explicit handling of regressions in control metrics. - 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 process, technique, hypothesis, data, and communication lessons every cycle, with an optional one-page A3 Report template for formal stakeholder communication. - Use Case: A team reduced API latency in a pilot but saw a regression in error rate. Use this Skill to decide to adjust before standardizing, document the poka-yoke mechanism, and produce the pdca-act.md artifact. ## Quick Start Ask the assistant to run the pdca-act step for the current work package using the verdict documented in pdca-check.md.

Frequently Asked Questions about pdca-act

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

FAQPage Schema
How do I close a PDCA cycle after the Check phase?▼

Run the Act step using the verdict from your pdca-check.md artifact. The decision tree routes success to standardize-and-scale, partial results to a new cycle with a refined hypothesis, and failures to a new cycle with corrected analysis.

What is Yokoten in Lean continuous improvement?▼

Yokoten is the Lean principle of horizontal deployment: propagating a proven improvement to analogous processes. The references file details a four-step process of identifying similar areas, adapting the solution, transferring the learning, and verifying adoption.

When should I standardize versus start a new PDCA cycle?▼

Standardize when the objective was met without regressions in control metrics. Start a new cycle when the hypothesis was wrong, implementation was incomplete, the goal was unrealistic, or external conditions invalidated the pilot data.

What is poka-yoke and why apply it before scaling?▼

Poka-yoke is error-proofing that prevents accidental reversion of an improvement, such as system constraints, automation, regression alerts, or prominent documentation. Without it, later changes can silently undo the gain.

What are the limitations of the PDCA Act step?▼

Act cannot compensate for a Check phase with poor data, and standardization ownership belongs to the team that owns the process. Rollouts affecting multiple teams require coordination outside this Skill's scope.