This skill is intentionally strict. It turns research, local evidence, competitive analysis, implementation reality, and product philosophy into verifiable artifacts that future agents and humans can use before planning or executing work.

<church_layout> Repo Church is the umbrella for machine- and operator-generated artifacts under <repo>/.church/:

Path	Purpose
`bible/`	Repo Bible packet — markdown doctrine/requirements, `_repo-bible-*.md` CLI tool reports, `vision-intake.html`, and `html/` (default output of `render-html`) for human review.
`runs/`	Local scratch exports (operators should keep this gitignored).
`README.md`	Operator map; created on first `scaffold` if missing.
`index.json`	Small manifest (`church_root`, `bible_dir` relative to repo root); refreshed by `scaffold`.

Defaults resolve under <repo>/.church/bible/ (override with --church-root, --bible-dir, or CHURCH_ROOT). One-time migration from .planning/commandments/: copy the tree into .church/bible/, or re-run generation with --legacy-planning-bible while reading old paths.

repo-bible