← Back to Skills Marketplace
Plan Do Check Act
by
brucezhu888
· GitHub ↗
· v1.2.0
· MIT-0
123
Downloads
0
Stars
1
Active Installs
6
Versions
Install in OpenClaw
/install plan-do-check-act
Description
PDCA workflow automation with session binding and progress recovery. Requires Python 3.6 and Git (optional).
Usage Guidance
This skill appears coherent for PDCA automation, but take these precautions before installing or running it:
- Use a dedicated workspace directory (the default is ~/pdca-workspace) and do not point the tool at system, home-root, or project root directories containing sensitive files. The scripts recursively scan the workspace and report on recently modified filenames and git status.
- Review archive/cleanup behavior and always run cleanup with --dry-run first to confirm what will be deleted. cleanup() will remove archived .md files older than the configured threshold.
- The skill uses subprocess calls to run Git (git status, git init). If you opt into git initialization, be aware it will create a .git repository under the chosen workspace.
- The skill asks for interactive confirmations in some flows (archive prompt). If you plan to let an agent invoke it autonomously, consider whether you want to permit non-interactive runs that could archive/delete files; avoid granting autonomous runs if you are uncomfortable with that.
- If you want higher assurance, inspect or run the bundled scripts locally in a safe test workspace before allowing the skill to operate on real project data.
If you want, I can highlight exact lines that perform file deletion, git operations, and workspace traversal so you can review them quickly.
Capability Analysis
Type: OpenClaw Skill
Name: plan-do-check-act
Version: 1.2.0
The skill implements a legitimate Plan-Do-Check-Act (PDCA) workflow for task management and progress tracking. It provides scripts (manage_plan.py, check_progress.py) to create checklists, monitor file modifications/Git status for activity, and archive completed tasks. The code uses standard Python libraries, lacks network exfiltration capabilities, and limits file operations to a user-defined workspace. While it contains a hardcoded Discord ID (1488795270769676318) in documentation and help strings, it is used strictly as a placeholder example for session binding logic.
Capability Assessment
Purpose & Capability
Name/description (PDCA workflow, Python 3.6+, optional Git) align with the included scripts. The bundled scripts implement step analysis, dependency checking, progress inference (via git and file mtimes), plan management, setup, archiving, and cleanup — all consistent with a PDCA workflow automation tool.
Instruction Scope
SKILL.md states the skill 'only operates on plan*.md files in the configured workspace', but several scripts (check_progress.py's get_recent_files, analyze_task_progress, and listing functions) walk the entire workspace and report on recently modified files and git status. Those routines do not read file contents broadly (they record paths and mtimes) but they do examine the workspace recursively and could surface or act on many files. Cleanup/archive functions operate on archive/*.md files and will permanently delete files when run without --dry-run if the archive age threshold is met (though archive() prompts for user confirmation when a plan isn't completed). The instructions reference an on-start trigger and session binding; some commands (e.g., manage_plan.py on-start) are suggested in docs — ensure you run only commands you understand.
Install Mechanism
No install spec (instruction-only skill). Code files are bundled with the skill and there are no remote downloads or install scripts that fetch external executables. This keeps on-disk changes limited to files the user runs locally (e.g., workspace creation, git init).
Credentials
The skill requests no environment variables or credentials. It interacts with the filesystem (workspace) and optionally runs Git commands; these are proportionate to its described purpose. There are no network endpoints, API keys, or secret access in the code.
Persistence & Privilege
always:false (not force-included). The skill can be invoked autonomously as is normal for skills, but it does not declare persistent system-wide changes or modify other skills. It can initialize a git repo in the workspace and delete archived files within the workspace; those are normal for a plan manager but require the user to choose a safe workspace.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install plan-do-check-act - After installation, invoke the skill by name or use
/plan-do-check-act - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.0
Added trigger conditions documentation: agent now knows to call manage_plan.py on-start when user asks about incomplete tasks, progress, or plan status
v1.1.1
Clarified Git is optional: updated setup wizard messages and documentation to make it clear PDCA works without Git
v1.1.0
Added setup wizard (scripts/setup.py) to guide users through initial setup: check dependencies, create workspace, create test plan, optional git init
v1.0.2
Security fixes: added requirements (Python 3.6+, Git optional), documented workspace scope, added --dry-run to cleanup, documented destructive operations
v1.0.1
Added agent workflow documentation: output plan content to user, report progress after each task completion
v1.0.0
Initial release: PDCA workflow automation with session binding, progress recovery, and multi-plan management
Metadata
Frequently Asked Questions
What is Plan Do Check Act?
PDCA workflow automation with session binding and progress recovery. Requires Python 3.6 and Git (optional). It is an AI Agent Skill for Claude Code / OpenClaw, with 123 downloads so far.
How do I install Plan Do Check Act?
Run "/install plan-do-check-act" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Plan Do Check Act free?
Yes, Plan Do Check Act is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Plan Do Check Act support?
Plan Do Check Act is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Plan Do Check Act?
It is built and maintained by brucezhu888 (@brucezhu888); the current version is v1.2.0.
More Skills