/extend — IWE Extensibility Catalog

Trigger: /extend, "what can I extend?", "how to configure a protocol", "how to add a custom step". Role: R6 Encoder. Single output: a map of what is available + specific instructions.

Algorithm

1. Identify the request scope

If an argument is provided (e.g. /extend day-open) → show only that protocol. If no argument is provided → show the full catalog.

2. Show the current customization state

ls {{WORKSPACE_DIR}}/extensions/*.md 2>/dev/null || echo "(no extensions)"
cat {{WORKSPACE_DIR}}/params.yaml 2>/dev/null

Report:

• Which extensions are already installed (✅)
• Which parameters have already been changed from defaults

3. Output the catalog

Extension points (files in extensions/)

For archgate.before and archgate.checks, the last instruction must produce ARCHGATE_EXTENSION: PASS or ARCHGATE_EXTENSION: BLOCK — <reason>. BLOCK is a normal content-level block. A loader or execution error is a separate failure. In archgate.after, ARCHGATE_EXTENSION: WARN — <reason> is allowed; the result of this Phase does not change the already-published verdict. An extension must not re-invoke the archgate lifecycle via load-extensions.sh archgate ...: the loader returns BLOCK for before/checks and WARN for after. If a corrupted or recursive file is present among archgate.after files, all other valid files still execute.

Multiple files for the same Hook — loaded in alphabetical order. Example: day-close.after.md + day-close.after.health.md — both will execute.

A file without a Hook name, such as extensions/verify.md, is not an extension point. Use one of the explicitly listed variants: before, checks, or after.

Parameters (params.yaml)

Day Open (memory/day-rhythm-config.yaml)

Custom Skills (.claude/skills/)

Create .claude/skills/<name>/SKILL.md — the Skill will be available as /<name>. Frontmatter: name, description, user_invocable: true. update.sh does not touch user-defined Skills (they are not in the Manifest).

Preservation. There is no built-in preservation mechanism for custom Skills: the .claude/skills/<name>/ directory is typically not under git (the workspace root is not a Repository), the Day Close (day-close.sh, "Backup" step) copies Memory, instructions, and agent rules — but not Skills. update.sh does not delete a Skill, but does not migrate it either, and /iwe-restore will not restore it. Until the template owner defines a Backup model, keep a copy of your Skills in a git Repository under your own control (for example, in a private {{GOVERNANCE_REPO}}) — otherwise moving to a new machine or reinstalling IWE will silently lose them.

4. Suggest the next step

Based on what is already configured, suggest what to add next.

No extensions at all:

"A good starting point is day reflection. Create extensions/day-close.after.md with 3 questions?"

Extensions exist, no morning ritual:

"Next step — extensions/day-open.before.md for morning preparation."

5. Create an extension (if requested)

If the user says "create" or "add" after viewing the catalog:

1. Clarify the content (or offer a Template)
2. Create the file in extensions/
3. Remind: the extension activates on the next protocol invocation

Sharing — Installing Someone Else's Extension

IWE extensions are plain Markdown files. To install:

cp ~/Downloads/day-close.after.health.md ${IWE_WORKSPACE:-$HOME/IWE}/extensions/

Name conflict (two files for the same Hook): Rename with a suffix: day-close.after.md + day-close.after.health.md. Both load in alphabetical order — no conflict.

Extension bundle format:

my-extension-pack/
  README.md                  # description, author, version
  extensions/
    day-close.after.md        # extension files
  params-defaults.yaml        # recommended parameters (not applied automatically)

Installing a bundle:

cp my-extension-pack/extensions/* ${IWE_WORKSPACE:-$HOME/IWE}/extensions/
# Review params-defaults.yaml and manually add the needed parameters to ${IWE_WORKSPACE:-$HOME/IWE}/params.yaml