---
title: SiteOps Skill Catalog — README
created: 2026-05-06
created_by: claude-code-opsman (Wave 3.4 of upgrade plan)
status: live
related:
  - "[[../../_Brain/README]]"
  - "[[_Log]]"
---

# SiteOps Skill Catalog

Canonical source of truth for all 12_SiteOps skills. Mirrors LFCS catalog pattern (`11_OpsMan_LFCS/Operations/skills/_README.md`).

Scope: site-specific operational artifacts that aren't bid-side (LFCS) or growth-side (RateRight). Examples:
- Site induction packs (white card, SWMS sign-on, site-specific briefs)
- ITP (Inspection & Test Plans) generation per pour / element
- Pre-pour checklists (assembled from standards + site context)
- Toolbox-talk records
- Defect-list templates

## Naming convention

`siteops-{verb}-{noun}` (mirrors LFCS `lfcs-*` pattern).

## SKILL.md template

Every skill follows the same structure as LFCS skills:

```
---
name:
description:
status: live | draft
---

# SKILL — {name}
## Purpose
## Trigger
## Inputs
## Behaviour
## Output format
## Hard rules
## Dependencies
## Failure modes
```

## Existing skills

| Skill | Trigger | Status |
|---|---|---|
| `siteops-induction-pack` | "Build induction pack for [site] [crew]" | live (v1) |
| `siteops-itp-generate` | "Generate ITP for [pour/element]" | live (v1) |

## Add/retire procedure

Follow the cross-lane convention in `_System/SKILLS.md`:
1. Create `siteops-<name>/SKILL.md` here.
2. Append row to `_System/SKILLS.md` § Lane: 12_SiteOps.
3. Append v-entry to `_Log.md` (this catalog) with reason for new skill.
4. If skill writes to Airtable, document in `## Airtable behaviour` section.

## Regression fixtures

Each new skill should have at least one fixture site/crew/pour for regression testing. Fixtures live alongside SKILL.md in a `fixtures/` subdir. Until SiteOps has 2+ live jobs, fixtures are template-based rather than real-job-based.