kaizen-improvement-system
Skill4 starsChanged 18 days agoMITView on GitHub
Use when auditing or improving the business-plan engine or any business plan, strategy, model, pitch, nonprofit plan, or execution framework it produces.
2 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- peterbamuhigire/chwezi-dev-enginetheir own version, first seen Nov 15, 2026
- peterbamuhigire/proposal-skillsedited, first seen Oct 17, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- peterbamuhigire/proposal-skills★ 1121% same
Wrote their own version · 1
- peterbamuhigire/chwezi-dev-engine★ 31same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository105 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- finance-policy-and-manualSkill
- governance-and-board-charterSkill
- grants-management-manualSkill
- hr-policy-manualSkill
- internal-controls-and-risk-frameworkSkill
- me-framework-documentSkill
- procurement-policy-and-manualSkill
- ecommerce-business-model-diagnosticSkill
- ecommerce-unit-economics-and-cross-border-margin-modelSkill
- ict-product-company-business-planSkill
- ict-services-firm-business-planSkill
- hospitality-hotel-restaurantSkill
- industry-guidesSkill
- east-african-englishSkill
- language-standardsSkill
- writing-qualitySkill
- demand-forecastingSkill
- digital-marketing-strategySkill
- entrepreneurial-demand-generationSkill
- marketing-plan-orchestratorSkill
- meta-accounting-finance-reviewSkill
- meta-agent-bankability-and-investor-readinessSkill
- meta-agent-revenue-recognition-policySkill
- meta-agent-sla-financial-controlsSkill
- meta-agent-valuation-adjustmentsSkill
- meta-agent-valuation-overlay-for-slaSkill
- meta-ai-bankability-and-investor-readinessSkill
- meta-ai-valuation-adjustmentsSkill
- meta-bankability-scoringSkill
- meta-financial-stress-testSkill
- meta-investment-committee-red-teamSkill
- meta-valuationSkill
- meta-pitch-preparationSkill
- meta-presentation-designSkill
- pitch-deckSkill
- meta-premium-go-to-marketSkill
- meta-pricing-strategySkill
- meta-website-investment-planningSkill
- meta-agent-board-and-investor-reportingSkill
- meta-board-and-investor-reportingSkill
- benchmark-methodologySkill
- business-plan-orchestratorSkill
- competitive-platform-analysisSkill
- competitive-report-structureSkill
- idea-testingSkill
- meta-business-model-designSkill
- meta-consulting-synthesisSkill
- meta-critical-thinking-business-logicSkill
- meta-digital-transformationSkill
- meta-due-diligenceSkill
- meta-international-market-entrySkill
- meta-living-plan-governanceSkill
- meta-market-validationSkill
- meta-monitoring-evaluationSkill
- meta-operational-readiness-due-diligenceSkill
- meta-quarterly-gameplanSkill
- meta-statisticsSkill
- meta-strategic-auditSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 8 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 33
Read the local adoption plan and the portfolio standard.
- Very specific: line 37
Create a P0/P1/P2 improvement backlog targeting 95/100.
- Distinctive: line 38
Run a small Build-Measure-Learn or PDCA experiment.
- Distinctive: line 56
Read and search are required.
- Distinctive: line 60
If evidence, model, source, reviewer, or tool is unavailable, return the narrowest qualified result, mark the gap as not assessed, and do …
- Distinctive: line 72
Never call a plan bankable or achievable without reconciled evidence, assumptions, finance, implementation, and risks.
- Distinctive: line 78
Only after the capped baseline is recorded may the engine run the improvement cycle.
- Distinctive: line 82
Run it twice when scope warrants: first for engine routing, models, references, validators, and handoffs.
- Distinctive: line 95
If a market test raises enquiries but worsens fulfilment capacity, retain the result as mixed evidence, keep the capacity guardrail, revise …
- Very specific: line 99
Every Kaizen cycle must begin with digital-research-engine source evaluation and source verification.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Kaizen Improvement System
Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com.
<!-- dual-compat-start -->Use When
- Auditing this engine or a plan, model, strategy, pitch, or execution framework.
- Converting assumptions, market feedback, KPI variance, or delivery lessons into a tested improvement.
Do Not Use When
- The task is only a single-skill safety audit.
- A current market, legal, tax, platform, or finance claim has not been routed to Digital Research and Chwezi where applicable.
Required Inputs
| Artefact | Source/provider | Required? | Purpose | If absent |
| Engine or product scope, audience, evidence pack, assumptions/model, current score, constraints, and target measures | Project and engine | yes | Set audit scope and improvement target | Stop, mark unassessed, or request the missing evidence |
Workflow
- Read the local adoption plan and the portfolio standard.
- Inventory routes, plan types, references, templates, models, examples, source registers, and release gates.
- Score doctrine, taxonomy, skill depth, applied proof, currency, output readiness, inclusivity, production fidelity, hygiene, routing, and integrity. Publish
min(raw score, 65)and record blockers. - For a product, test the thesis, customer or beneficiary logic, market evidence, operating model, ten-point local operational readiness, financial reconciliation, implementation capacity, risks, governance, and audience fit.
- Create a P0/P1/P2 improvement backlog targeting 95/100; each action needs owner, experiment, measure, evidence, and rollback.
- Run a small Build-Measure-Learn or PDCA experiment. If evidence fails, stop, recover the safe baseline, and revise the hypothesis.
- Re-run model, source, anti-slop, workbook, operational-readiness, and release gates as applicable; standardise successful learning and schedule the next review.
Outputs
| Artefact | Consumer | Acceptance condition |
| Capped audit, evidence gaps, blockers, 95/100 plan, experiment log, and standardisation record | Planner, reviewer, and release owner | Scores, owners, evidence, decisions, rollback, and re-audit date are explicit |
Evidence Produced
| Evidence | Format | Acceptance condition |
| Assumption ledger, model/source checks, experiment result, gate results, and before/after review | Markdown, workbook, or validator output | Another reviewer can reproduce the decision and verify the change |
<!-- dual-compat-end -->Capability Contract
Read and search are required. Audits are read-only by default; edits require explicit authority and permission. Route current facts to Digital Research and finance doctrine to Chwezi.
Degraded Mode
If evidence, model, source, reviewer, or tool is unavailable, return the narrowest qualified result, mark the gap as not assessed, and do not certify bankability or readiness.
Decision Rules
| Condition | Action | Failure or risk avoided |
| Material assumption has no evidence | Stop the claim and run a validation test | False certainty |
| A test improves one metric but harms cash, mission, quality, or capacity | Reject, recover, or escalate | Local optimisation |
| A change passes gates and improves the target measure | Standardise it and re-audit | Lost learning |
Quality Standards
Never call a plan bankable or achievable without reconciled evidence, assumptions, finance, implementation, and risks. Never turn a book example into a client fact.
Mandatory 65-to-95 gate
The first pass is an initial analysis, not a certification: calculate the raw result,
publish min(raw_score, 65), and keep every unassessed dimension and blocker visible.
Only after the capped baseline is recorded may the engine run the improvement cycle.
The cycle must target 95/100 with a named root cause, one reversible change, owner,
measure, guardrail, stop/rollback rule, acceptance evidence, and re-audit date. A
polished plan or book-derived idea is not a score increase until the evidence passes.
Run it twice when scope warrants: first for engine routing, models, references,
validators, and handoffs; then for the individual plan, model, pitch, or strategy.
Anti-Patterns
- Adding initiatives without stopping or sequencing others. Fix: expose capacity trade-offs.
- Treating a KPI as learning without a decision rule. Fix: define threshold, action, and counter-metric.
- Writing a polished plan before testing assumptions. Fix: run a small validation experiment.
- Hiding uncertainty in prose. Fix: label assumptions, gaps, confidence, and countercases.
- Closing an improvement with no evidence. Fix: require a validated artefact or test.
Worked Example
If a market test raises enquiries but worsens fulfilment capacity, retain the result as mixed evidence, keep the capacity guardrail, revise the offer or process, and re-test before changing the plan.
Mandatory Digital Research currentness gate
Every Kaizen cycle must begin with digital-research-engine source evaluation
and source verification. Record scope, dates, freshness class, support status,
uncertainty, and review date for current market, legal, policy, technology,
platform, finance, and lifecycle claims; quarantine unsupported claims as
NOT_ASSESSED. Apply the portfolio Kaizen currentness gate.
References
- Local adoption plan
- Portfolio standard: resolve
digital-research-enginethrough the global engine-routing table, then readdocs/continuous-improvement/portfolio-kaizen-standard-2026-08.md. skills/meta-strategy/meta-market-validation/skills/meta-strategy/meta-living-plan-governance/- Book-driven commercial system and validation - whole-system trade-offs, validation, replication, GTM, cash, and currentness.
- Marketing Plan Handbook operating loop - adaptive customer-first planning, segmentation, strategy-to-program alignment, forecasting, budgeting, metrics, and control.
- Book-driven Kaizen Wave 3 - hypotheses, capacity/cash guardrails, experiments, dashboards, and responsible AI economics.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

