Supports iterative planning, design, and analysis workflows.
Install
mkdir -p .claude/skills/pdca-lowyshin && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17554" && unzip -o skill.zip -d .claude/skills/pdca-lowyshin && rm skill.zipInstalls to .claude/skills/pdca-lowyshin
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Unified skill for managing the entire PDCA cycle. Auto-triggered by keywords: "plan", "design", "analyze", "report", "status". Replaces legacy /pdca-* commands. Use proactively when user mentions PDCA cycle, planning, design documents, gap analysis, iteration, or completion reports. Triggers: pdca, 계획, 설계, 분석, 검증, 보고서, 반복, 개선, plan, design, analyze, check, report, status, next, iterate, gap, 計画, 設計, 分析, 検証, 報告, 计划, 设计, 分析, 验证, 报告, planificar, diseño, analizar, verificar, planifier, conception, analyser, vérifier, rapport, planen, Entwurf, analysieren, überprüfen, Bericht, pianificare, progettazione, analizzare, verificare, rapporto Do NOT use for: simple queries without PDCA context, code-only tasks.Key capabilities
- →Create Plan documents for features
- →Generate Design documents based on plans
- →Provide implementation guides for the Do phase
- →Perform gap analysis between design and implementation
- →Automate code fixes and re-verification in Act phase
- →Generate completion reports for features
How it works
The skill manages the PDCA cycle by creating and updating documentation files for each phase. It uses specific agents like 'gap-detector' and 'pdca-iterator' for analysis and iteration.
Inputs & outputs
When to use pdca
- →Planning a new iteration
- →Analyzing project results
- →Reporting on process status
About this skill
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 (start implementation) | /pdca do user-auth |
analyze [feature] | Run Gap analysis (Check phase) | /pdca analyze user-auth |
iterate [feature] | Auto improvement iteration (Act phase) | /pdca iterate user-auth |
report [feature] | Generate completion report | /pdca report user-auth |
archive [feature] | Archive completed PDCA documents | /pdca archive user-auth |
status | Show current PDCA status | /pdca status |
next | Guide to next phase | /pdca next |
Action Details
Output Path: docs/01-plan/features/{feature}.plan.md
Product thinking checkpoint (Gstack office-hours)
Before finalizing the plan, the agent must:
- Challenge the premises of the request.
- Ask the user at least one "Taste Decision" question.
- Consider the "10-star version" vs the "shameful MVP".
design (Design Phase)
- Verify Plan document exists (required - suggest running plan first if missing)
- Create
docs/02-design/features/{feature}.design.md - Use
design.template.mdstructure + reference Plan content - Create Task:
[Design] {feature}(blockedBy: Plan task) - Update .bkit-memory.json: phase = "design"
Output Path: docs/02-design/features/{feature}.design.md
do (Do Phase)
- Verify Design document exists (required)
- Provide implementation guide based on
do.template.md - Reference implementation order from Design document
- Create Task:
[Do] {feature}(blockedBy: Design task) - Update .bkit-memory.json: phase = "do"
Guide Provided:
- Implementation order checklist
- Key files/components list
- Dependency installation commands
analyze (Check Phase)
- Verify Do completion status (implementation code exists)
- Call gap-detector Agent
- Compare Design document vs implementation code
- Calculate Match Rate and generate Gap list
- Create Task:
[Check] {feature}(blockedBy: Do task) - Update .bkit-memory.json: phase = "check", matchRate
Output Path: docs/03-analysis/{feature}.analysis.md
iterate (Act Phase)
- Check results (when matchRate < 90%)
- Call pdca-iterator Agent
- Auto-fix code based on Gap list
- Auto re-run Check after fixes
- Create Task:
[Act-N] {feature}(N = iteration count) - Stop when >= 90% reached or max iterations (5) hit
Iteration Rules:
- Max iterations: 5 (adjustable via bkit.config.json)
- Stop conditions: matchRate >= 90% or maxIterations reached
report (Completion Report)
- Verify Check >= 90% (warn if below)
- Call report-generator Agent
- Integrated report of Plan, Design, Implementation, Analysis
- Create Task:
[Report] {feature} - Update .bkit-memory.json: phase = "completed"
Output Path: docs/04-report/{feature}.report.md
archive (Archive Phase)
- Verify Report completion status (phase = "completed" or matchRate >= 90%)
- Verify PDCA documents exist (plan, design, analysis, report)
- Create
docs/archive/YYYY-MM/{feature}/folder - Move documents (delete from original location)
- Update Archive Index (
docs/archive/YYYY-MM/_INDEX.md) - Update .pdca-status.json: phase = "archived", record archivedTo path
- Remove feature from activeFeatures
Output Path: docs/archive/YYYY-MM/{feature}/
Documents to Archive:
docs/01-plan/features/{feature}.plan.mddocs/02-design/features/{feature}.design.mddocs/03-analysis/{feature}.analysis.mddocs/04-report/features/{feature}.report.md
Important Notes:
- Cannot archive before Report completion
- Documents are deleted from original location after move (irreversible)
- Feature name must match exactly
status (Status Check)
- Read
.bkit-memory.json - Display current feature, PDCA phase, Task status
- Visualize progress
Output Example:
📊 PDCA Status
─────────────────────────────
Feature: user-authentication
Phase: Check (Gap Analysis)
Match Rate: 85%
Iteration: 2/5
─────────────────────────────
[Plan] ✅ → [Design] ✅ → [Do] ✅ → [Check] 🔄 → [Act] ⏳
next (Next Phase)
- Check current PDCA phase
- Suggest next phase guide and commands
- Confirm with user via AskUserQuestion
Phase Guide:
| Current | Next | Suggestion |
|---|---|---|
| None | plan | /pdca plan [feature] |
| plan | design | /pdca design [feature] |
| design | do | Implementation start guide |
| do | check | /pdca analyze [feature] |
| check (<90%) | act | /pdca iterate [feature] |
| check (>=90%) | report | /pdca report [feature] |
| report | archive | /pdca archive [feature] |
Template References
Templates loaded from imports are used when executing each action:
| Action | Template | Purpose |
|---|---|---|
| plan | plan.template.md | Plan document structure |
| design | design.template.md | Design document structure |
| do | do.template.md | Implementation guide structure |
| analyze | analysis.template.md | Analysis report structure |
| report | report.template.md | Completion report structure |
Task Integration
Each PDCA phase automatically integrates with Task System:
Task Creation Pattern:
┌────────────────────────────────────────┐
│ [Plan] {feature} │
│ ↓ (blockedBy) │
│ [Design] {feature} │
│ ↓ (blockedBy) │
│ [Do] {feature} │
│ ↓ (blockedBy) │
│ [Check] {feature} │
│ ↓ (blockedBy, Check < 90%) │
│ [Act-1] {feature} │
│ ↓ (on iteration) │
│ [Act-N] {feature} │
│ ↓ (Check >= 90%) │
│ [Report] {feature} │
│ ↓ (after Report completion) │
│ [Archive] {feature} │
└────────────────────────────────────────┘
Agent Integration
| Action | Agent | Role |
|---|---|---|
| analyze | gap-detector | Compare Design vs Implementation |
| iterate | pdca-iterator | Auto code fix and re-verification |
| report | report-generator | Generate completion report |
Usage Examples
# Start new feature
/pdca plan user-authentication
# Create design document
/pdca design user-authentication
# Implementation guide
/pdca do user-authentication
# Gap analysis after implementation
/pdca analyze user-authentication
# Auto improvement (if needed)
/pdca iterate user-authentication
# Completion report
/pdca report user-authentication
# Check current status
/pdca status
# Guide to next phase
/pdca next
Legacy Commands Mapping
| Legacy Command | PDCA Skill |
|---|---|
/pdca-plan | /pdca plan |
/pdca-design | /pdca design |
/pdca-analyze | /pdca analyze |
/pdca-iterate | /pdca iterate |
/pdca-report | /pdca report |
/pdca-status | /pdca status |
/pdca-next | /pdca next |
/archive | /pdca archive |
Auto Triggers
Auto-suggest related action when detecting these keywords:
| Keyword | Suggested Action |
|---|---|
| "plan", "planning", "roadmap" | plan |
| "design", "architecture", "spec" | design |
| "implement", "develop", "build" | do |
| "verify", "analyze", "check" | analyze |
| "improve", "iterate", "fix" | iterate |
| "complete", "report", "summary" | report |
| "archive", "cleanup", "store" | archive |
⚡ Optimization Integration
When using this skill for critical tasks, please run it within a /native-trace context to capture performance data for self-improvement via /aioptimize.
When not to use it
- →Simple queries without PDCA context
- →Code-only tasks without a PDCA framework
Limitations
- →Cannot archive before Report completion
- →Max iterations for auto-improvement is 5
- →Requires a matchRate of >= 90% to stop iteration
How it compares
This skill provides a structured, automated workflow for the PDCA cycle, integrating documentation and agent-based analysis, unlike a manual, ad-hoc approach.
Compared to similar skills
pdca side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| pdca (this skill) | 0 | 3mo | Review | Intermediate |
| linear | 10 | 1mo | No flags | Beginner |
| zapier-workflows | 11 | 8mo | Review | Beginner |
| attio-skill-generator | 7 | 7mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by LowyShin
View all by LowyShin →You might also like
linear
lobehub
Linear issue management guide. Use when working with Linear issues, creating issues, updating status, or adding comments. Triggers on Linear issue references (LOBE-xxx), issue tracking, or project management tasks. Requires Linear MCP tools to be available.
zapier-workflows
davila7
Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to "run" any process. Also handles Perplexity-based research and Google Sheets data tracking.
attio-skill-generator
kesslerio
Generate use-case-specific Attio workflow skills from templates. Use when creating new skills for lead qualification, deal management, customer onboarding, or custom Attio workflows.
automation-brainstorm
MacroMan5
Interactive workflow design advisor for Power Automate, n8n, Make, Zapier and other platforms. Guides users through planning automation workflows with smart questions about triggers, actions, data flow, and error handling. Uses research sub-agent to find best practices and generates detailed implementation plan. Triggers when user mentions "create workflow", "build flow", "design automation", "need ideas for", or describes workflow requirements without having a complete design.
daily-briefing
anthropics
Start your day with a prioritized sales briefing. Works standalone when you tell me your meetings and priorities, supercharged when you connect your calendar, CRM, and email. Trigger with "morning briefing", "daily brief", "what's on my plate today", "prep my day", or "start my day".
jira
davila7
Use when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues, check sprint status, or manage their Jira workflow. Triggers on keywords like "jira", "issue", "ticket", "sprint", "backlog", or issue key patterns.