standup

name	standup
owner	baseline
description	Read-only release + backlog recap. Reports the last release, commits-since-tag classified by conventional-commit type with the semver bump they trigger and pushed-vs-origin state, the backlog bucketed (open/picked-up/dropped with epic parent→child nesting), and condensed open questions — then recommends the next pickup. Invoke any time (on demand) to plan a release or choose the next thing to build; a compact form is also surfaced at session start. Not a workflow phase; never writes CHANGELOG; never starts or commits work.

standup — where are we, what's next

A read-only recap utility in the family of audit-baseline / rca: it reads state and reports, it never mutates. Run it whenever you sit down to plan a release or pick the next piece of work. It is not a workflow phase — it does not enter the Track Guard ordering and never blocks a commit.

What it answers

1. Shipped — the last released version (from CHANGELOG.md / the latest tag).
2. Staged but unreleased — every commit since the last tag, classified by conventional-commit type, with the aggregate semver bump those commits will trigger (read from .releaserc.json at runtime, so it never drifts from the release config) and the pushed-vs-origin state.
3. Backlog — entries bucketed open / picked-up / dropped, with epic children nested under their parent.
4. Open questions — pending-questions.md condensed to id + question + blocker.
5. Recommended next pickup — assembled in main context (see Article II below).

How to run

The mechanical recap is produced by a deterministic helper:

node .claude/skills/standup/gather.mjs [--root <repo-root>]

It prints a JSON StandupRecap (release, backlog, pendingQuestions, degraded). It degrades gracefully — on a non-git tree, a repo with no tags, or missing memory files it names the missing precondition in degraded[] and never throws.

Article II — where the judgment lives

Per CLAUDE.md Article II, decisions live in main context. The helper only gathers the mechanical recap; it does not pick what to build next. After reading the helper's JSON, the recommendation — the single suggested next pickup and its one-line rationale (smallest unblocker first) — is reasoned out in main context, not emitted by the helper. The session-start surface (the memory_session_start hook) shows only the compact mechanical recap plus a pointer back to /standup; the full judgment recommendation is on-demand here.

Constraints

• Read-only. Reads git, .releaserc.json, CHANGELOG.md, and the memory files. Writes nothing.
• Never writes CHANGELOG.md — semantic-release owns it in CI.
• Never starts, stages, or commits work — it recommends; you act.
• Deterministic core — identical repo + memory state yields identical helper output (no clock read in the core path).