Guide a six-step kaizen cycle with 5 Whys to improve workflows.
npx skills add https://github.com/kouko/monkey-skills --skill kaizen-kouko
Please help me install this Agent Skill. Skill: kaizen Source: https://github.com/kouko/monkey-skills/tree/main/philosophers-toolkit/skills/kaizen Command: npx skills add https://github.com/kouko/monkey-skills --skill kaizen-kouko
Helps teams and individuals surface and eliminate everyday waste and friction by guiding a structured, small-step improvement cycle so that processes become faster, less error-prone, and easier to maintain without large disruptive changes.
Run a kaizen cycle on my PR review process by describing the current flow, typical timings, and the single biggest source of delay.
High-intent search queries and answers about installing and using this skill.
To reduce waste in code review, apply a six-step continuous improvement cycle: map the current state, find delays, run 5 Whys root-cause analysis, propose minimal changes, verify with before/after metrics, and standardize successful fixes.
The 5 Whys root-cause analysis is a focused questioning technique used in process improvement to iteratively ask why a problem occurs, moving past symptoms to identify the fundamental underlying cause of workflow delays and waste.
Apply continuous improvement to shorten meeting times by guiding a structured, small-step cycle: grasp current meeting flow, identify waste, validate with measurable before/after timings, and implement incremental changes without large disruptive rewrites.
Yes, kaizen optimizes deployment pipelines by identifying unnecessary effort and delays through sequential prompts, proposing minimal reversible improvements, and validating changes with measurable before and after metrics to stabilize deployment steps.
Continuous improvement works for streamlining documentation workflows by surfacing everyday friction through a guided cycle, applying root-cause analysis to find bottlenecks, and standardizing small, validated changes for easier maintenance.
Small-step process improvement avoids proposing large-scale rewrites or wholesale changes, focusing instead on incremental, measurable adjustments, which means it may not be suitable for resolving fundamental architectural failures requiring complete workflow redesigns.
timurgaleevDetect performance regressions by comparing page load timings and resource metrics.
adryanmoldokkr32-pixelMerge pull requests, monitor CI, deploy to production, and verify health with canary checks.
mt-krainskiManage Jira issue transitions, branch creation, and pull requests.
DhumitechImplement small, verifiable code changes with iterative testing.
