Ho System, Actually Build the software. Develop the judgment.

dandori (段取り)

procedure
depth 3/3 − deeper + surface

The preparation that turns a resolved plan into exact, runnable instructions before any building starts.

Preparation; staging; the carpenter's setup, the chef's mise en place. Operationally: the discipline and format for translating a ho's resolved Think phase into executable agent-task specs. Exists as a standalone skill (lean, no Ho System assumptions) and embedded in the kamae-5 skill (Ho-scoped naming, paths, commit format). The load-bearing bridge of the operating layer.

The Dandori Bridge. The translation from a ho's Think phase to executable specs is a craft move with a name: dandori (段取り—preparation, staging). It is operationalized twice:

  • Embedded in the kamae-5 skill (dandori/ toolkit: DANDORI.md, FORMAT.md, KOKOROE.md, examples)—the Ho System-scoped variant that authors constitutive children during per-ho authoring.
  • As a standalone skill—the lean variant for tasks outside any ho.

The five translation moves (decisions → interface specifications; architectural commitments → file boundaries; out-of-scope items → Do Not entries; deferred discoveries → Stop Conditions; verification dependencies → ordering) live in FORMAT.md. The five kokoroe guidelines the executing agent operates under (context-first, spec as authorization, verify by command, halt and surface, honor the boundary) live in KOKOROE.md and install at the project level via CLAUDE.md.

Dandori is not a utility skill. It is the load-bearing bridge of the operating layer—the mechanism by which the two registers stay separated in practice. The skill catalog should present it at that altitude.