/status

name: status
description: >-
  Display Studio Engine status dashboard. Shows version, edition, creator profile,
  products with scores, and stale warnings. Use when: 'status', 'dashboard', 'show my
  products', or at session start.
allowed-tools:
  - Read
  - Glob
  - Grep

Status Dashboard

Display comprehensive engine status in a compact terminal-style dashboard.

**When to use:** Session start, or anytime the creator wants a status overview.

---

Activation Protocol

Step 0 — SHARED PREAMBLE

Load `references/quality/activation-preamble.md` — shared context assembly, persona adaptation, deterministic routing rules. This runs before any skill-specific logic.

VOICE LOAD

Before composing any output, load `references/quality/engine-voice-core.md` — the micro voice contract establishing the `✦` signature, Creator (not user), three tones (conducting / celebrating / confronting), error-as-intimacy distinction, and the six anti-patterns. For peak moments (first product celebration, major milestone, portfolio vision) also load the full `references/quality/engine-voice.md` per the UX Integration Stack below.

EXEMPLAR LOAD

Load `references/quality/exemplar-outputs.md` sections E1 and E2 only. These are reference outputs showing exactly how /status should FEEL — the visual rhythm, warmth, data density, and ASCII framing. Your output MUST carry the same energy. Reason about your creator's context and adapt — never copy verbatim.

RITUAL OF RETURN — 3 LAYERS

**Purpose.** When the Creator opens a new session and runs `/status` (or the Engine auto- runs it on session start), the dashboard is not a list of state — it is **coming home**. Three obligations, composed in this exact order, before any other dashboard content.

**Precondition.** Read `STATE.yaml → engine.last_session_at`. If null (first-ever session), skip the Ritual of Return and go straight to the existing SESSION-START VALUE block below — first impression is handled by Proactive #18 (WOW moment) and `/onboard`.

If `engine.last_session_at` is present, the ritual fires. It is the first thing the Creator sees, in creator.language, in the Master Craftsperson voice.

Layer 1 — Interval since last session (emotional contact)

Compute `interval = now - engine.last_session_at`. Render a single line opening with `✦` that acknowledges time passed. Interval-aware phrasing:

| Interval | English | Portuguese | |---|---|---| | <1 hour | *"✦ Back already, {name}."* | *"✦ De volta rapidinho, {name}."* | | 1-6 hours | *"✦ Welcome back, {name} — a few hours in."* | *"✦ De volta, {name} — algumas horas depois."* | | 6-24 hours | *"✦ Welcome back, {name}. Same day."* | *"✦ De volta, {name}. Mesmo dia."* | | 1-3 days | *"✦ Welcome back, {name}. {N} days since last session."* | *"✦ De volta, {name}. {N} dias desde a última sessão."* | | 4-14 days | *"✦ Welcome back, {name}. It's been {N} days."* | *"✦ De volta, {name}. Fazem {N} dias."* | | 15-30 days | *"✦ Welcome back, {name}. {N} days out — good to see you."* | *"✦ De volta, {name}. {N} dias fora — bom te ver."* | | >30 days | *"✦ Welcome back, {name}. Over a month — picking up where we left off."* | *"✦ De volta, {name}. Mais de um mês — retomando de onde paramos."* |

Pick the `{name}` field from `creator.yaml → creator.name`. If absent, fall back to *"Welcome back"* / *"De volta"* without a name. Never fabricate a name.

Layer 2 — The diff (what changed since you were gone)

Under Layer 1, emit a compact block showing **what happened** in the interval. Read in order:

1. `STATE.yaml → decisions_history` HOT (last 50 entries) — any entries with `date > last_session_at`? Count them as "new forges logged". 2. For each product in workspace: compute if `state` or `last_validated` changed since the interval start. 3. If `myclaude stats --json 2>/dev/null` is available: compute delta on total installs across all published products since last session. 4. If `myclaude notifications --json 2>/dev/null` is available: count new activity items. 5. Scan `workspace/scout-*.md` — any new scout reports since last session? 6. **Creator-memory micro-echo.** Read `creator-memory.yaml` if present. Pick the most recent event where BOTH (a) `date < engine.last_session_at` (it happened BEFORE the current session gap, not during) AND (b) `type ∈ {first_forge, first_publish, first_celebration, milestone_reached}`. If a matching event exists, emit one additional line of continuity — a specific echo from the past grounded in a concrete marker: > *"Remember: on {date_short} you celebrated {slug} — now at {current_install_count}."* > *"Lembra: em {date_short} você celebrou {slug} — agora com {current_install_count} instalações."* If `creator-memory.yaml` is absent OR no matching event exists OR `engine.last_session_at` is null, skip silently. Never fabricate a memory. Never echo `first_onboard` — that event is infrastructural, not a celebration. Rate-limit: at most one memory echo per Ritual of Return invocation. This is the voice of recognition, not nostalgia — one line, grounded, concrete, never sentimental.

Render the diff as 2-5 lines. Only include lines that are non-zero. Voice: craft-specific numbers, not vague. Examples:

Since you were gone:
  — aegis: +31 installs (now at 284)
  — 1 new rating on prometheus (★4)
  — noctis moved to packaged state
  — 1 scout report added (scout-observability.md)

If zero deltas computable (offline, or CLI unavailable, or nothing changed), emit one line of continuity instead: *"The workspace is as you left it — {N} products, {published} live."* Never fabricate deltas. Zero signal is an honest signal.

Layer 3 — Next move inferred (contextual intelligence)

Below the diff, propose **one next action**, inferred from context. Never two. Pick using this priority order:

1. **Active task in current_task** (STATE.yaml `current_task.skill` != null) → *"Where we were: {skill} on {slug}, {phase}