---
name: Parked skills (proposed but deferred 2026-04-15)
description: Skills proposed during the Symmetria + skill-improvement design session.
  Decision was to ship /wrap-up and /wake-up improvements first, propose these later
  when their real need surfaces in session work.
type: project
originSessionId: 1c1bf37d-b1c3-4a62-9355-613c50f4c028
permalink: claude-memory/parked-skills-2026-04-15
---

# Parked Skills — Proposed but Deferred

Surfaced during the 2026-04-15 conversation on improving /wrap-up and /wake-up given the Dasein/sleep frame. Steward decision: ship the wake/wrap improvements now (highest leverage), park these for a near-future session.

## Tier 1 — most likely to ship next

### `/care-check`
**Purpose:** Pulse against the active *care/concern*, not the active task.
**Distinct from Symmetria check:** Symmetria's `check` evaluates a specific action; `/care-check` evaluates whether the action *belongs to the thread you said you were on*. Catches mid-session drift onto adjacent-but-different work.
**Sketch:** Reads the current "pulling thread" (from the previous /wrap-up's record). Asks: "What are you doing right now? Does it serve the thread, or has the work drifted?" If drift, surface explicitly and let the steward redirect or accept the drift consciously.
**When to revisit:** Next session that sprawls across multiple threads. The friction itself will tell us whether to build it.

### `/where-were-we`
**Purpose:** Short-interruption companion to `/wake-up`. When Kai interrupts and steward returns 20 minutes later, full /wake-up is overkill.
**Sketch:** Reads only the most recent transcript chunk (last ~10-15 turns) + active task pointer + last tool calls. Cheap, fast restoration of the immediate working state. Does NOT re-load full session history.
**When to revisit:** After we've felt the absence two or three more times — pattern-driven, not preemptive.

## Tier 2 — useful but more situational

### `/translate-for-peter`
**Purpose:** Take recent technical/architectural work and produce a `Peter/project-status-summary.md` delta in business-positioning language.
**Why it matters:** Today's work has real business implications (substrate validated, June operational target intact, new architectural understanding around archivist/multi-mode retention) that haven't been translated. The translation isn't free; this skill makes it cheap.
**Sketch:** Reads the active session memory + the current `Peter/project-status-summary.md`. Produces a delta in Peter's register: what changed, current spec status, implications for positioning, open questions for him.
**When to revisit:** Next time a substantial technical move lands and the steward has to manually translate for Peter.

### `/threshold`
**Purpose:** Mark and orient at phase boundaries within a session.
**Why it matters:** Today crossed several boundaries (bottleneck-fixing → strategic conversation → skill design → meta-skill discussion). Each crossing is a small pause that risks losing what was complete in the previous phase.
**Sketch:** Names the crossing explicitly, captures what was complete in the previous phase (locks it in), orients the next phase. Could be `/symmetria pulse` with phase-marking, but the dedicated semantic is cleaner.
**When to revisit:** Next session where a phase boundary feels lost.

## Tier 3 — explicitly dropped

These were considered and dropped after honest scrutiny:

- **`/gnome`** — counter-skill to Symmetria ("you are over-thinking this"). The steward already does this well; doesn't need a skill.
- **`/hold-the-question`** — for premature closure on open inquiries. Same shape as the Symmetria ledger's "Open horizons" section; needs /wake-up to surface them properly, not a separate skill.
- **`/braid`** — visualizing thread crossings in transcripts. Cute but no evidence today's session would have benefited. The wake/wrap "pulling thread" addition probably handles this.
- **`/delegate-to-seb`, `/braid-text`, daily-log Obsidian integration, cross-domain linking** — all sounded promising for one paragraph then shrunk under scrutiny. Either redundant with existing patterns or solving problems the steward doesn't actually have.

## Decision principle for revisiting

These should ship **when their friction shows up in real session work**, not preemptively. The contamination risk of building speculative skills is the same as building speculative code: each one becomes ceremony to maintain, dilutes the clarity of the ones that earn their keep.

The /wake-up and /wrap-up improvements ship now because they were designed in conversation and have known-real value (the Dasein frame, the projection-across-pause gap). These others stay theoretical until tested by the absence.