# /om build system scaffold added to tenant template

## Why this note exists

The monorepo added a guided `/om build` operation (Steps 2-3 of the Building-Systems Scaffold
task) that sequences the full platform runbook for authoring an Organization Model System end
to end. This train mirrors a thinner, Codify-ceremony-framed variant of that operation into the
tenant template. Tenant projects author OM via the Codify ceremony (not the platform PR-review
runbook), so the tenant variant is scoped accordingly.

Changes in this train:

- New operation file `.claude/skills/om/operations/build.md` (Codify-framed, 8 phases).
- `metadata.promptSignals` in `.claude/skills/om/SKILL.md` extended with four build-intent
  phrases: `build a system`, `design a system`, `create a system that`, `system architecture`.
- `## Operations` table added to `.claude/skills/om/SKILL.md` with the `build` EXECUTE row.
- Build-intent routing branch added to the Decision Tree section of `SKILL.md` so free-text
  build intent routes to `/om build` before the 5-bucket read/write buckets.

## Applies to

- All template-derived projects that ship the `om` skill (`.claude/skills/om/SKILL.md`).
- Any project where an agent might express intent to build or design a new System.

## Required actions

1. Pull template changes so the new `build.md` operation file and the updated `SKILL.md` are
   present in `.claude/skills/om/`.
2. No package baseline bumps required -- this is a pure agent-scaffold change (no published
   package version involved).
3. No `pnpm install` needed unless the `/git-sync` pull also brings unrelated baseline changes.

## Verification

- `.claude/skills/om/operations/build.md` is present.
- `.claude/skills/om/SKILL.md` contains the `build` row in the `## Operations` table.
- `.claude/skills/om/SKILL.md` `metadata.promptSignals.phrases` includes `build a system`,
  `design a system`, `create a system that`, and `system architecture`.
- Saying "build a system for lead gen" in chat triggers `/om` and routes to `/om build` without
  requiring the explicit `/om build` subcommand.

## Not handled by /git-sync

- No dependency bumps or `pnpm install` required for this change alone.
- Any project-local documentation that references how to add a new System should be updated by
  the maintainer to point at `/om build` as the guided entry point rather than manual Codify
  Level-A alone.
