What problem does it solve? After running a PDCA pilot, teams often declare success or failure based on gut feeling rather than data. This Skill structures the Check phase of the PDCA cycle, comparing actual pilot results against the baseline and SMART objectives defined in the Plan phase, and producing a data-backed verdict. ## Core Features & Use Cases - Objective vs. Result Comparison: Builds a metrics table contrasting baseline, SMART target, and actual pilot outcome, including control metrics to detect regressions. - Statistical Significance Validation: Applies Run Chart rules (8 consecutive points), sample-size minimums, T-test, Mann-Whitney U, or historical range checks to distinguish real improvement from noise. - Structured Verdict and Recommendation: Produces a direct conclusion (hypothesis confirmed, refuted, or mixed) plus a recommendation for the Act phase: standardize, adjust, retry, or revert. - Use Case: After a two-week pilot reducing API p95 latency, use this Skill to verify the sample size is sufficient, confirm the improvement exceeds natural process variation, and generate the pdca-check.md artifact with a clear verdict. ## Quick Start Ask the assistant to run the PDCA Check step on your completed pilot data and compare the results against the Plan objectives to produce a verdict.