plan-do-check-act
PDCA workflow automation with session binding and progress recovery. Requires Python 3.6 and Git (optional).
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/brucezhu888/plan-do-check-actPlan-Do-Check-Act Skill
This skill implements the PDCA (Plan-Do-Check-Act) workflow to ensure tasks are systematically planned and executed.
Requirements
- Python 3.6+ - Required for all scripts
- Git - Optional - Only used for progress tracking. PDCA works perfectly without Git - it will use file modification times instead.
Setup Guide (First Time)
After installing, run the setup wizard:
# Run interactive setup
python3 scripts/setup.py
The wizard will:
- Check Python and Git dependencies
- Create workspace directory (default:
~/pdca-workspace) - Create a test plan
- Optionally initialize Git for progress tracking
- Show next steps
Manual Setup
If you prefer manual setup:
# 1. Create workspace directory
mkdir -p ~/pdca-workspace
# 2. Create a test plan
cd ~/pdca-workspace
manage_plan.py create "My First Plan" "Task 1" "Task 2" "Task 3"
# 3. Verify it works
manage_plan.py check plan.md
# 4. (Optional) Set up git for progress tracking
git init
Security Notes
- Workspace Scope: Only operates on
plan*.mdfiles in the configured workspace directory - Destructive Operations:
cleanupcommand deletes archived files older than specified days (default 7) - User Confirmation: Archive operation prompts for confirmation if plan is not completed
- Dry Run: Use
cleanup --dry-runto preview before deleting - Autonomous Invocation: Should require user confirmation before cleanup/archive operations
Core Process
1. Plan
When receiving a user task, create plan.md:
- Break down the task into executable subtasks
- Record the session ID
- Mark priorities and dependencies
2. Do
Execute tasks according to plan.md:
- Check off each completed task
[x] - Mark in-progress tasks as
[>] - Record issues during execution
3. Check
After all tasks are completed:
- Check for any missed items
- Verify output meets expectations
- Identify areas for improvement
4. Act
Based on check results:
- Fix identified issues
- Update plan.md with learnings
- Archive or iterate
plan.md Template
# Task Plan: [Task Name]
**Session:** discord:1488795270769676318
**Created:** YYYY-MM-DD HH:MM
**Status:** IN_PROGRESS | COMPLETED | PAUSED
## Current Task
> Task 3 - Implement Login API (in progress)
## Checklist
- [x] Task 1 - Database Design
- [x] Task 2 - User Model Creation
- [>] Task 3 - Implement Login API (in progress)
- [ ] Task 4 - Implement Registration API
- [ ] Task 5 - Unit Testing
## Notes
Records during execution...
## Check Results
Fill in after completion...
Trigger Scenarios
Core Logic: Step Analysis
After receiving a task, quickly analyze how many steps are needed:
1-2 steps → Execute directly, no plan
- "Rename a file"
- "Delete that test file"
3-5 steps → Optional plan (ask user)
- "Help me build a login feature"
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-brucezhu888-plan-do-check-act": {
"enabled": true,
"auto_update": true
}
}
}Related Skills
Use Dingding
Skill by brucezhu888
feishu-file-upload
Upload and send local files to Feishu chats. Requires Feishu app credentials (app_id/app_secret) in ~/.openclaw/openclaw.json. Use when user asks to send/share/upload files (CSV, PDF, Excel, images, ZIP) to Feishu. Supports chat_id (groups), open_id/user_id (users), and email recipients.
Dingtalk Workspace
Skill by brucezhu888
use-cursor
Manage Cursor CLI tasks via tmux with security hardening