git:20260610.be2a852 to git:20260610.c15894f

32 added, 4 removed. Audit A to A.

---

name: client-retire

description: "Archive a client's patterns and mark them as historical. Use when retiring a client or archiving its knowledge for future reference."

effort: low

model: haiku

keywords: [archive, retire, client, historical, cleanup]

task_strategies: [migration]

stream_affinity: [roadmap]

argument-hint: "[client-slug]"

group: execution

allowed-tools:

- Bash

- Read

- Write

- Glob

- Grep

- AskUserQuestion

status: stable

growth_stage: evergreen

---

+ # Client Retire

-

- This skill's full procedure is in a separate file for startup performance (ADR-034).

- Read and execute `../../procedures/client-retire.md` resolved against this skill's base directory (the path announced when the skill loads) — i.e. `{base-dir}/../../procedures/client-retire.md`. This form is valid in both the repo layout and the deployed-plugin layout.

- If the path doesn't resolve, use Glob to find `**/procedures/client-retire.md`.

+ 1. Identify the client to retire from `$ARGUMENTS` or current client context.

+ 2. **Primary path (ruflo available):**

+ ```bash

+ source "$HOME/.claude/scripts/cf-env.sh"

+ ```

+ Query memory DB for all patterns tagged with this client via `cd $HOME && $CF memory search --query "client:{name}"`. List them with confidence scores.

+ 3. **Fallback path (ruflo unavailable):**

+ Read the client's `~/.claude/projects/{project-hash}/memory/MEMORY.md` and list all documented patterns.

+ 4. For each pattern, categorize:

+ - **High-confidence + transferable** → keep active, remove client-specific lock

+ - **High-confidence + client-specific** → archive with `status: historical`

+ - **Low-confidence** → archive or flag for deletion

+ 5. Run the archival: tag patterns with `archived: true` and `archived_date: {today}`.

+ 6. Suggest updating `~/.claude/memory/portfolio.md` to mark the client as retired.

+ 7. **Never delete anything** — only tag and archive. Deletion is a human decision.

+ 8. **Backup knowledge** after archiving:

+ ```bash

+ "$HOME/.claude/scripts/backup-knowledge.sh"

+ ```

+ Skip silently if the script doesn't exist.

+ ## Rules

+ - **Ask for clarification whenever you need it.** If you're unsure which patterns to keep active vs archive, or the client scope is ambiguous — ask. Don't guess.