Browse / Software development / jidoka

jidoka

nikopermi

Plan-first pipeline for Claude Code: research -> grill -> outline -> llm-code-review

Open nikopermi/jidoka → Checked against the four rules.

Does not say

no agent config and no instruction file at the root.

In its own words

README.mdnikopermi/jidoka

Plan-first pipeline for Claude Code. Four skills, one contract: research the code, grill the design, outline the phases, review at two gates. Nothing gets built until the plan survives an adversarial read.

Jidoka: stop the line when a defect appears, fix the cause, resume. Applied to agent work, the cheapest place to stop is the plan.

Pipeline

Each stage writes one file into the task folder and stops. The next stage reads it. The folder path docs/plans/ACTIVE/ / is the contract between stages; move finished folders out of ACTIVE/ however you like.

Why this shape

  • Questions before search. Agents skip scoping about half the time when not forced. research hard-stops until the user answers.
  • Thin outlines. A 1000-line plan diverges from the code. A 100-line outline with per-phase scope and verify commands gets built and checked.
  • Review the plan, not just the diff. One wrong line in an outline becomes many wrong lines of code. The same failure-class list runs at both gates.
  • Fresh reviewer. The session that wrote the work does not review it.

Companion

llm-code-review complements the built-in /code-review; it does not replace it. Run both before merge.

The whole README. Open the repo ↗

Read from the repository's git tree on 2026-08-17.