Menu
Kaizen (改善): every process has waste; eliminate it incrementally.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Canonical b00t reviewer capability — adversarial multi-framework code/datum review. Shared across all harnesses (Claude Code, opencode, Hermes, b00t-cli). Loaded via: b00t learn reviewer, or by harness-specific role supplements.
Remove AI-generated artifacts from code. Three-phase certainty-graded cleanup. Use after any AI implementation session or before PR creation.
8-phase agile workflow — strategy→ideate→brainstorm→plan→work→review→compound→pulse. State machine with FOL-guarded transitions, gh-issues backlog, executable just harness. Inspired by everyinc/compound-engineering-plugin.
Australian crypto tax treatment per ATO guidance QC 53725. Crypto assets are CGT assets under ITAA 1997 s 108-5. Each disposal triggers CGT event A1. Covers personal-use exception, trading stock test, and the 50% CGT discount.
Australian R&D Tax Incentive (RDTI) — ITAA 1997 Division 355. Covers eligibility criteria for core and supporting R&D activities, registration with AusIndustry/IP Australia, expenditure categories, offset rates, and the company size threshold test.
Evidence graph construction for tax audit trails. Each Satisfies check emits EvidenceNode structs with Blake3 content hashes. Evidence chains are tamper-evident and link legislative citations to factual findings.
| name | kaizen |
| type | skill |
| hint | Continuous improvement — small compounding changes beat big rewrites |
| version | 1.0.0 |
| tags | ["transferable","improvement","iteration","retrospective","compound","incremental","waste","kaizen"] |
| tier | sm0l |
| complexity | 2 |
| description | Kaizen (改善): every process has waste; eliminate it incrementally. |
Kaizen (改善, Japanese for "continuous improvement") teaches that every process has waste and you should eliminate it incrementally. Apply after every task: what was slow? what caused errors? what would I do differently? The retrospective is not optional — skipping it is how technical debt compounds. In code, prefer small focused PRs over big rewrites. Each PR equals one improvement.
Measure before and after — if you cannot measure it, you cannot improve it. Three questions drive the practice: What worked? What didn't? What one thing changes next iteration?
Use kaizen after every task, every PR, every sprint. Any time you hear "we will fix it later" is a signal that kaizen should be applied now.
