This is a structured implementation of the PDCA (Plan-Do-Check-Act) continuous improvement cycle. You define a problem with measurable baselines, test a hypothesis with a small change, measure the results, then either standardize what worked or adjust and iterate. The examples show realistic scenarios like reducing Docker build times from 45 to 4.5 minutes over two cycles, where the first iteration hit the target but revealed a new bottleneck. It's most useful when you have a specific problem to solve and want to avoid the trap of making too many changes at once without knowing what actually worked. The framework forces you to document everything and set concrete success criteria, which sounds tedious but pays off when you're on cycle three trying to remember why you made certain decisions.

skills.sh installs
1.2K
GitHub stars
1.8K
last updated
Aug 21, 2026

Install

$ npx -y skills add neolabhq/context-engineering-kit --skill plan-do-check-act --agent claude-code

Installs into .claude/skills of the current project.

Files

Plan-Do-Check-Act (PDCA)

Apply PDCA cycle for continuous improvement through iterative problem-solving and process optimization.

Description

Four-phase iterative cycle: Plan (identify and analyze), Do (implement changes), Check (measure results), Act (standardize or adjust). Enables systematic experimentation and improvement.

Usage

/plan-do-check-act [improvement_goal]

Variables

  • GOAL: Improvement target or problem to address (default: prompt for input)
  • CYCLE_NUMBER: Which PDCA iteration (default: 1)

Steps

Phase 1: PLAN

  1. Define the problem or improvement goal
  2. Analyze current state (baseline metrics)
  3. Identify root causes (use /why or /cause-and-effect)
  4. Develop hypothesis: "If we change X, Y will improve"
  5. Design experiment: what to change, how to measure success
  6. Set success criteria (measurable targets)

Phase 2: DO

  1. Implement the planned change (small scale first)
  2. Document what was actually done
  3. Record any deviations from plan
  4. Collect data throughout implementation
  5. Note unexpected observations

Phase 3: CHECK

Sponsors

Details

Repository
github.com/neolabhq/context-engineering-kit
Category
Productivity & Planning
First seen
Jun 3, 2026

More from neolabhq/context-engineering-kit

All 63
1jamesrochabrun avatarprd-generatorjamesrochabrun/skillsGenerate comprehensive Product Requirements Documents (PRDs) for product managers. Use this skill when users ask to "create a PRD", "write product requirements"1.2Kskills.sh installs
2nexscope-ai avataramazon-seasonal-planningnexscope-ai/amazon-skillsSeasonal sales calendar — Prime Day, Black Friday, Q4 prep, inventory planning, promotion scheduling1.2Kskills.sh installs
3product-on-purpose avatardeliver-prdproduct-on-purpose/pm-skillsCreates a comprehensive Product Requirements Document that aligns stakeholders on what to build, why, and how success will be measured. Use when specifying feat1.1Kskills.sh installs
4eachlabs avatarfloor-plan-generationeachlabs/skillsGenerate floor plans and architectural layouts using each::sense AI. Create apartment designs, house layouts, office spaces, retail stores, restaurants, and 3D 952skills.sh installs
5alirezarezvani avatarcode-to-prdalirezarezvani/claude-skillsReverse-engineer any codebase into a complete Product Requirements Document (PRD). Analyzes routes, components, state management, API integrations, and user int798skills.sh installs
6sickn33 avatarplan-writingsickn33/antigravity-awesome-skillsplan writing772skills.sh installs