← ClaudeAtlas

plumb-line-bootstraplisted

Use when setting up a project with the plumb-line discipline — interviews the builder to find their source-truth layer and layering, generates a domain-neutral ruleset, and installs parameterized enforcement (boundary check, test gate, pre-commit gate, branch guard) for the project's language. Ships no default layers and invents no answers.
slopstopper/plumb-line · ★ 4 · Code & Development · score 70
Install: claude install-skill slopstopper/plumb-line
# Bootstrap a project with plumb-line Part of the four-skill flow: learn the discipline with `plumb-line-method`, set the project up here, review changes with `plumb-line-audit`, and apply findings with `plumb-line-remediate`. REQUIRED READING FIRST: `reference/portable-principles.md` and `adapters/adapter-contract.md` (plugin root). If either file cannot be read, stop immediately and report which file is missing. Do not proceed from memory. ## Two entries: full bootstrap vs. declaration-only (mid-audit) This skill has two entry modes. **Full bootstrap** — the builder asked for setup — runs every step below. **Declaration-only** — `plumb-line-audit` invoked this skill because the project declares no architecture and the audit needs that context before proceeding — runs a deliberately two-minute detour: - Ask ONLY interview questions 1–3 (layers + direction; source-truth layer; composition root). The audit needs the declaration, not the ceremony. - Write the ruleset from those answers (Step 3), marking every section the interview did not reach as `planned` — an un-asked question must not read as an answered one. - Skip Step 4, Step 4b, and Step 6's audit offer entirely: no enforcement install, no primitive offer, nothing added to the project beyond the ruleset file. Those belong to a full bootstrap run — name it as the follow-up in the report's TODOs. - Emit the Step 5 report header with one extra line — `entry: declaration-only` — then return the baton: the