pdca
Skill66 starsChanged 7 months agoApache-2.0View on GitHub
Unified skill for managing the entire PDCA cycle. Supports Plan → Design → Do → Check → Act workflow with automatic phase progression.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- AlexeyShirshov/skillstheir own version, first seen Nov 1, 2026
- unclejobs-ai/second-claude-codetheir own version, first seen Oct 13, 2026
- popup-studio-ai/bkit-claude-codetheir own version, first seen Oct 8, 2026
- tupe12334/instincttheir own version, first seen Aug 17, 2026
- ww-w-ai/bkit-claude-codetheir own version, first seen Aug 14, 2026
- twhsi/skillstheir own version, first seen Jul 21, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- popup-studio-ai/bkit-claude-code★ 605same name
- ww-w-ai/bkit-claude-code★ 605same name
- twhsi/skills★ 259same name
- ww-w-ai/bkit-codex★ 69same name
- unclejobs-ai/second-claude-code★ 41same name
- AlexeyShirshov/skills★ 15same name
- tupe12334/instinct★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository42 other files it gives its agents.
- auditSkill
- batchSkill
- bkend-authSkill
- bkend-cookbookSkill
- bkend-dataSkill
- bkend-guidesSkill
- bkend-mcpSkill
- bkend-quickstartSkill
- bkend-securitySkill
- bkend-storageSkill
- bkit-rulesSkill
- bkit-templatesSkill
- btwSkill
- code-reviewSkill
- controlSkill
- deploySkill
- desktop-appSkill
- development-pipelineSkill
- dynamicSkill
- enterpriseSkill
- gemini-cli-learningSkill
- loopSkill
- mobile-appSkill
- output-style-setupSkill
- phase-1-schemaSkill
- phase-2-conventionSkill
- phase-3-mockupSkill
- phase-4-apiSkill
- phase-5-design-systemSkill
- phase-6-ui-integrationSkill
- phase-7-seo-securitySkill
- phase-8-reviewSkill
- phase-9-deploymentSkill
- plan-plusSkill
- pm-discoverySkill
- qa-phaseSkill
- rollbackSkill
- simplifySkill
- skill-createSkill
- skill-statusSkill
- starterSkill
- zero-script-qaSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
19 rules. 0 are common, 8 are distinctive, and 11 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
11
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 80
Check if docs/01-plan/features/{feature}.plan.md exists
- Distinctive: line 81
If not, create based on plan.template.md
- Very specific: line 83
Context Anchor Generation: After generating Plan document, extract Context Anchor (WHY/WHO/RISK/SUCCESS/SCOPE) from Executive Summary, …
- Very specific: line 85
Write as ## Context Anchor table between Executive Summary and Section 1.
- Distinctive: line 96
Verify Plan document exists
- Very specific: line 98
Create Task: [Design] {feature} (blockedBy: Plan)
- Distinctive: line 106
Ask user which option to select before proceeding
- Distinctive: line 109
Verify Design document exists
- Very specific: line 111
Create Task: [Do] {feature} (blockedBy: Design)
- Distinctive: line 112
Full Upstream Context Loading: Read ALL upstream documents:
- Very specific: line 124
Parse --scope parameter: If --scope module-1 provided, filter implementation guide to matching modules only from Design's Session Guide
- Distinctive: line 126
Ask user to confirm scope before starting implementation
- Very specific: line 133
After gap-detector analysis, also call bkit_iterate MCP tool for quantitative gap measurement:
- Very specific: line 136
If matchRate < 90%, recommend calling /pdca iterate
- Distinctive: line 139
Check results (when matchRate < 90%)
- Very specific: line 143
Call bkit_iterate MCP tool for automated gap analysis:
- Very specific: line 147
Call bkit_iterate again to re-check
- Very specific: line 152
When running QA, call bkit_qa_run MCP tool:
- Distinctive: line 157
If passRate < 95%, fix issues and re-run
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
PDCA Skill
Unified Skill for managing PDCA cycle. Supports the entire Plan → Design → Do → Check → Act flow.
Arguments
| Argument | Description | Example |
plan [feature] | Create Plan document | /pdca plan user-auth |
design [feature] | Create Design document | /pdca design user-auth |
do [feature] | Do phase guide | /pdca do user-auth |
analyze [feature] | Run Gap analysis (Check) | /pdca analyze user-auth |
iterate [feature] | Auto improvement (Act) | /pdca iterate user-auth |
report [feature] | Generate completion report | /pdca report user-auth |
archive [feature] | Archive PDCA documents | /pdca archive user-auth |
status | Show current status | /pdca status |
next | Guide to next phase | /pdca next |
Action Details
plan (Plan Phase)
- Check if
docs/01-plan/features/{feature}.plan.mdexists - If not, create based on plan.template.md
- Create Task:
[Plan] {feature} Context Anchor Generation: After generating Plan document, extract Context Anchor (WHY/WHO/RISK/SUCCESS/SCOPE) from Executive Summary, Requirements, and Risk sections. Write as
## Context Anchortable between Executive Summary and Section 1.Dimension Content WHY Core problem being solved WHO Target users/stakeholders RISK Top 3 risks identified SUCCESS Measurable success criteria SCOPE In-scope / out-of-scope boundary
design (Design Phase)
- Verify Plan document exists
- Create
docs/02-design/features/{feature}.design.md - Create Task:
[Design] {feature}(blockedBy: Plan) - Context Anchor Embed: Copy Plan's
## Context Anchortable to Design document top (between header metadata and ## 1. Overview). If Plan has no Context Anchor, skip gracefully. - Generate 3 Architecture Options:
- Option A — Minimal Changes: Least modification, maximum reuse
- Option B — Clean Architecture: Best separation of concerns
- Option C — Pragmatic Balance: Good boundaries without over-engineering
- Present comparison table with trade-offs (complexity, maintainability, effort, risk)
- Ask user which option to select before proceeding
do (Do Phase)
- Verify Design document exists
- Provide implementation guide
- Create Task:
[Do] {feature}(blockedBy: Design) - Full Upstream Context Loading: Read ALL upstream documents:
- PRD (docs/00-pm/{feature}.prd.md) — WHY context
- Plan (docs/01-plan/features/{feature}.plan.md) — Context Anchor, Success Criteria
- Design document — architecture decisions
- Decision Record Chain Display:
Decision Record Chain [PRD] Target: {segment} — {rationale} [Plan] Architecture: {option} — {rationale} [Design] Pattern: {approach} — {rationale} - Display Context Anchor from Design document header
- Parse --scope parameter: If
--scope module-1provided, filter implementation guide to matching modules only from Design's Session Guide - Ask user to confirm scope before starting implementation
analyze (Check Phase)
- Call gap-detector agent
- Compare Design vs implementation
- Calculate Match Rate
- Create Task:
[Check] {feature} - After gap-detector analysis, also call
bkit_iterateMCP tool for quantitative gap measurement:- This tool compares design document vs actual implementation
- Returns matchRate percentage and specific gaps with file references
- If matchRate < 90%, recommend calling
/pdca iterate
iterate (Act Phase)
- Check results (when matchRate < 90%)
- Call pdca-iterator agent
- Auto-fix and re-verify
- Max 5 iterations
- Call
bkit_iterateMCP tool for automated gap analysis:- Input: feature name, project directory, target match rate (default 90%)
- Tool returns gaps with specific file:line references
- Fix the identified gaps
- Call
bkit_iterateagain to re-check - Repeat until matchRate >= 90% or max 5 iterations
- Server tracks iteration count internally
qa (QA Phase)
When running QA, call bkit_qa_run MCP tool:
- Input: feature name, project directory, test levels [1,2,3,4,5]
- The tool auto-detects test framework (jest/vitest/playwright)
- L1: Unit tests, L2: API tests, L3-L5: E2E/browser tests (if playwright installed)
- Review results: passRate, coverage, defects
- If passRate < 95%, fix issues and re-run
report (Completion Report)
- Verify Check >= 90%
- Call report-generator agent
- Create completion report
- Load ALL upstream documents for comprehensive reporting:
- PRD — compare original value proposition vs delivered value
- Plan — compare planned Success Criteria vs actual results
- Design — note architecture decisions and any deviations
- Analysis — include final Match Rate
- Include Decision Record summary and Success Criteria final status
PDCA Flow
[Plan] ✅ → [Design] ✅ → [Do] ✅ → [Check] 🔄 → [Act] ⏳ → [Report] 📋
↑_________|
(if < 90%)References
${extensionPath}/templates/plan.template.md${extensionPath}/templates/design.template.md${extensionPath}/templates/analysis.template.md${extensionPath}/templates/report.template.md
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

