chatbi-buildlisted

Procedural runbook for deriving a build plan from a requirement, invoked by /chatbi-build-from-requirement. Reads blueprint (Source/Metrics/Layers/Tooling) + source_inventory + model_registry + semantic layer, derives an ordered ODS->DWD->DWS->ADS build plan (agent reasoning, no derivation lib), validates plan shape via chatbi_harness.build_plan, chains /chatbi-maintain-model per model, routes protected points to the human, and hands off to /chatbi-analyze. Orchestrator trust layer (SEM-003/META-008). Carries reusable procedure, not easily-stale facts.
lostinheaven-knt/chatbi-harness · ★ 0 · AI & Automation · score 60

Install: claude install-skill lostinheaven-knt/chatbi-harness

# chatbi-build Build runbook for the requirement-driven build workflow. This runbook is a **prompt / procedure artifact**, not executable code. Where a deterministic primitive exists in `.claude/lib/chatbi_harness/build_plan.py` or `bootstrap.py` / `config.py` / `adapters/`, this runbook names it; the live derivation + maintain-model chaining path is exercised manually (no live MySQL or maintain-model in CI). ## 0. Sources this runbook binds to - Lib surface: `chatbi_harness.build_plan` (`BuildPlan`, `ModelEntry`, `LayerRule`, `read_model_registry`, `collect_known_models`, `validate_build_plan`, `validate_layer_dependency`, `append_model_registry`) + `chatbi_harness.bootstrap` (`read_source_inventory`, `merge_source_inventories` - Q4). - Reused primitives: `chatbi_harness.load_effective_config` (`config.py`), `chatbi_harness.adapters.select_adapter` (`adapters/`), `chatbi_harness.policy.decide` (`policy.py`), `chatbi_harness.harness_state.write_state` / `read_state` (`harness_state.py:100,63`), `chatbi_harness.fail_closed` / `GateError` (`gates.py:143-167`). - Schema: `.claude/schemas/build-plan.schema.json` (the single contract for `validate_build_plan`, mirrors `impact-manifest.schema.json`). - Trust boundary: orchestrator = derive + chain + human-in-loop + handoff. No governed model authoring, no answer, no approval (SEM-003/META-008). ## 1. Step 1 - Read requirement + DW state (pure read) **Goal:** parse the requirement and read the current Ware