pdca-cycle

pdca-cycle is a skill for Claude Code from konglong87/methodology-skills. It costs 45 tokens per session (2,415 once invoked), scanned A, original, MIT.

A four-step improvement loop: plan a change, try it, check the result, and adjust what happens next. PDCA stands for Plan, Do, Check, Act, and is also called the Deming Cycle.

In plain words
What is it for?
Use it to test new processes, improve performance or quality, reduce costs, and increase customer satisfaction over repeated iterations.
Why use it?
It prevents teams from making a change once and assuming it worked. Repeating the loop helps improve quality and processes through small, evidence-based adjustments.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it to test new processes, improve performance or quality, reduce costs, and increase customer satisfaction over repeated iterations.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/konglong87/methodology-skills/pdca-cycle
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add konglong87/methodology-skills --skill pdca-cycle
Clone the repo
git clone --depth 1 https://github.com/konglong87/methodology-skills

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for pdca-cycle

README.md
[![agentmods](https://agentmods.dev/badge/skills/konglong87/methodology-skills/pdca-cycle/github.svg)](https://agentmods.dev/skills/konglong87/methodology-skills/pdca-cycle)
Your own site
<a href="https://agentmods.dev/skills/konglong87/methodology-skills/pdca-cycle"><img src="https://agentmods.dev/badge/skills/konglong87/methodology-skills/pdca-cycle/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for pdca-cycle

Your own site · 80×15
<a href="https://agentmods.dev/skills/konglong87/methodology-skills/pdca-cycle"><img src="https://agentmods.dev/badge/skills/konglong87/methodology-skills/pdca-cycle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,415 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00045 $0.02415
Opus 5 $0.00023 $0.01208
Sonnet 5 $0.00009 $0.00483
Haiku 4.5 $0.00005 $0.00242

Measured 9d ago against content hash 69d98669b91b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

pdca-cycle scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/pdca-cycle/SKILL.md · 320 lines

How it starts

The opening of the file, as written. The whole thing — 320 lines — stays where its author put it; the contents beside it link to each section on GitHub.

PDCA 循环

前置协议

环境检测

PROJECT_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || echo "unknown")
BRANCH=$(git branch --show-current 2>/dev/null || echo "unknown")
COMMIT=$(git rev-parse --short HEAD 2>/dev/null || echo "unknown")

echo "PROJECT: $PROJECT_ROOT"
echo "BRANCH: $BRANCH"
echo "COMMIT: $COMMIT"

前置技能检查

# 检查前置工件
GOAL_ARTIFACT="memory/artifacts/goal-oriented/latest.json"
MVP_ARTIFACT="memory/artifacts/mvp-first/latest.json"

if [ -f "$GOAL_ARTIFACT" ]; then
  echo "FOUND: goal-oriented artifact"
fi

if [ -f "$MVP_ARTIFACT" ]; then
  echo "FOUND: mvp-first artifact"
fi

mkdir -p memory/artifacts/pdca-cycle

PDCA 循环

Overview

PDCA 循环(Plan-Do-Check-Act)是一种持续改进的方法论,通过计划、执行、检查、处理四个阶段的循环,不断优化流程和结果。

核心价值

  • 数据驱动决策
  • 小步快跑,快速迭代
  • 持续改进,螺旋上升
  • 降低试错成本

起源: 戴明环(Deming Cycle),由 W. Edwards Deming 推广

When to Use

适用场景

  • 迭代任务,需要持续改进
  • 质量保障和流程优化
  • 新方案试点验证
  • 数据驱动的决策
  • 性能优化、成本降低
  • 用户满意度提升

不适用场景

  • 一次性、无需改进的任务
  • 紧急情况,需要立即行动

The Process

digraph pdca {
    rankdir=TB;

    Plan [label="Plan\n计划", shape=box, style=filled, fillcolor="#c8e6c9"];
    Do [label="Do\n执行", shape=box, style=filled, fillcolor="#bbdefb"];
    Check [label="Check\n检查", shape=box, style=filled, fillcolor="#fff9c4"];
    Act [label="Act\n处理", shape=box, style=filled, fillcolor="#f8bbd0"];

    Plan -> Do [label="制定计划"];
    Do -> Check [label="收集数据"];
    Check -> Act [label="分析结果"];
    Act -> Plan [label="下一轮循环", style=dashed];
}

四阶段详解

Plan(计划)

  • 明确目标和指标
  • 分析现状与差距
  • 制定具体行动计划
  • 预估风险和应对方案

Do(执行)

  • 小范围试点
  • 严格按照计划执行
  • 收集执行过程中的数据
  • 记录问题和观察

Check(检查)

  • 对比预期与实际结果
  • 分析偏差原因
  • 提取经验教训
  • 数据可视化呈现

Act(处理)

  • 标准化成功做法
  • 改进不足之处
  • 规划下一个循环
  • 扩大应用范围

Cycle Checklist

使用以下检查清单确保每个阶段完整执行:

Plan 阶段

  • 明确目标和衡量指标
  • 收集现状数据
  • 分析根本原因(可用鱼骨图、5 Whys)
  • 制定具体行动计划
  • 确定责任人和时间节点
  • 预估风险和应对措施

Do 阶段

  • 选择小范围试点区域
  • 准备所需资源
  • 严格按照计划执行
  • 收集过程数据(时间、成本、质量)
  • 记录遇到的问题和异常
  • 保持试点环境可控

Check 阶段

  • 对比实际结果与预期目标
  • 分析差异原因
  • 验证方案有效性
  • 提取成功经验和失败教训
  • 数据可视化(图表、报告)
  • 团队讨论并达成共识

Read the full file on GitHub · 320 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 320 lines · 45 tokens per session scan A 69d98669b91b

Subscribe to this mod's changes

pdca-cycle is a skill published in the GitHub repository konglong87/methodology-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 2,415 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

importing-a-codebase

Use when the repo holds real source code but no specs: the existing-codebase branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for empty workspaces (starting-a-new-project) or feature work in a specced project (brainstorming).

JetBrains/thinkrail · 69 tokens

starting-a-new-project

Use when the workspace is empty — no code yet — and the user brings a raw idea: the brand-new branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for features in an existing project — use brainstorming instead.

JetBrains/thinkrail · 61 tokens

todos

This chat has a shared, live TODO plan — your tasks for the conversation, which the user also edits. Read this skill and reach for the todo tools whenever a request takes more than a couple of steps. It covers the plan model (group = task, items = its steps; loose items are the user's lane), how to work it: propose…

JetBrains/thinkrail · 127 tokens

writing-workflow-skills

Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.

JetBrains/thinkrail · 60 tokens

brainstorming

Use this BEFORE any creative or feature work: building a new feature, adding functionality, changing behavior, or making a nontrivial design decision. Turns the user's request into a validated design — recorded as a spec-graph task-spec — before any implementation. Do not skip this because a change looks small.

JetBrains/thinkrail · 65 tokens

reviewing-changes

Use when a review package asks you to review a plan step's change set (todo.startReview): you are the REVIEWER, not the author. How to judge an agent-written diff, file findings with addreviewcomment, and settle with exactly one reviewverdict.

JetBrains/thinkrail · 59 tokens