kaizen
Kaizen
Every mistake or correction is signal. This skill captures it immediately — before the turn ends and the context is lost — as a short, permanent note in kaizen/.
The philosophy (from Japanese manufacturing): small, continuous improvements compound. A 5-10 line note written now can save hours later.
When to invoke
Invoke when you detect any of these signals:
| Signal | Examples |
|---|---|
| Explicit correction | "no", "wrong", "not like that", "undo that", "that's incorrect" |
| Path redirect | User asks you to stop and restart differently after you've made progress |
| Self-correction | You catch an error mid-task and have to backtrack significantly |
| Implicit correction | User re-explains something you already got wrong; visible frustration |
More from yldgio/vibe-grimoire
pre-mortem
>-
13create-prd
Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue, Azure DevOps work item, or local file. Use when the user wants to create or write a PRD, create a product requirements document, design a new feature, or capture requirements.
11setup-repo
>-
11prd-slice
Break a PRD into independently-deliverable work items (vertical slices / tracer bullets) and create them in Azure DevOps, GitHub Issues, or Jira. Use when a user wants to convert a PRD into implementation tickets, decompose a product spec into trackable slices, create work items from requirements, or break down a PRD for any issue tracker — even if they don't say "vertical slice" or "tracer bullet".
11plan-from-prd
Turn a PRD into a multi-phase, local Markdown implementation plan using tracer-bullet vertical slices, saved to ./plans/. Use when the user wants to create an implementation plan from a PRD, plan phases from a PRD, break a PRD into development phases, or mentions "tracer bullets" or "implementation phases". For creating tracker work items (GitHub Issues, Azure DevOps, Jira) use the prd-slice skill instead.
11tdd
>-
9