implementation-harness-customizelisted

Use when the user wants to discover and set up the implementation harness's customization features — phrases like "customize the harness", "what can I customize", "set up the hooks / guard / preambles", "harness feature walkthrough", "implementation-harness:implementation-harness-customize". Walks the `custom/` extension-point catalog one feature at a time: explains each, and for the ones the user wants, activates the opt-in file (.example → real) and helps DRAFT its content. Also invoked by create (all features) and upgrade (only features new since the install) so users always meet the features. Requires a scaffolded `.harness/`.
RyanMKrol/claude-skills · ★ 0 · AI & Automation · score 73

Install: claude install-skill RyanMKrol/claude-skills

# Customize the harness — feature walkthrough over the `custom/` overlay You walk the user through the harness's supported customization surface — the `custom/` overlay — one feature at a time, so nothing has to be discovered by reading source or (worse) by forking `loop.sh`. For each feature the user wants, you **activate** it (copy its `.example` stub to the real filename) and **help them draft the content** (interview → write the real file). Everything lives in `.harness/custom/`, which the harness upgrade **never** overwrites — so customizing this way keeps the install on a clean upgrade path. Read this whole file, then execute in order. ## 0. Pre-flight - Require a harness: `.harness/scripts/loop.sh` and `.harness/custom/` must exist. If not, send the user to `implementation-harness:implementation-harness-create` (fresh install) and stop. - **Determine scope** from `$ARGUMENTS`: - `--since <version>` (e.g. `--since 1.24.0`) → walk ONLY catalog features whose `since:` is **newer** than `<version>` (this is how `upgrade` shows a user just what's new since their install). Compare versions numerically (major.minor.patch). If none are newer, say "no new customization features since `<version>`" and stop. - no argument → walk the **whole** catalog. - Read the installed version for context: `cat .harness/.harness-version 2>/dev/null`. - Locate the shipped `.example` stubs — prefer the installed ones under `.harness/custom/`; if one is missing (an install