Feature
Standup.
A read-only recap of where a project stands and what to pick up next, on demand and at session start.
§ I
where are we, what's next.
Every planning session starts the same way. You read the changelog, scan git log against the last tag, open the backlog, hold it all in your head, then guess what is next.
Standup does the reading. One command turns the scattered state of a repository into one structured recap, so the question you actually care about, what to work on next, is the only one left to answer.
§ II
what it reads
The recap is assembled from the repository itself, not from anything you maintain by hand.
- the last shipped release.
- every commit since that tag, classified by conventional-commit type, with the version bump it will trigger.
- whether those commits are pushed, or still only local.
- the backlog, bucketed into open, picked-up, and dropped, with epics nested under their parent.
- the open questions, condensed to one line each.
§ III
the readout
The point of standup is the artifact it prints. Here is a real one, read from this repository.
shipped v0.16.0
unreleased 1 commit since v0.16.0 (next bump: minor)
feat(skills) add standup recap skill (40 to 41) minor
upstream ahead 1, not pushed
backlog 7 open, 0 picked-up, 0 dropped
epic baseline-v1 thought-compiler (open, 6 children)
open threat / value tier config dial
open promote review skills to oracle-bound checkers
... and 4 more
open questions Q-002, Q-007, Q-008
recommended next
tier config dial. small, foundational, it unblocks the
slice-b checkers that the rest of the epic depends on.§ IV
two modes
Standup shows up where you need it, without a setup step.
Run it on demand with /standup when you sit down to plan a release or choose the next thing to build. A compact version of the same recap also appears at the top of every session, so you start already knowing where you left off. The two stay out of each other's way: the session-start line is the short form, the on-demand command is the full readout above.
§ V
gather vs recommendation
The recap has two halves, and they are held to different standards.
The gather step is deterministic. The same repository state always reads the same way, so the facts in the readout are reproducible, not a guess. The recommended next pickup is the one judgment call, and it is reasoned in context rather than emitted by the helper. Standup draws the line on purpose: it reports what is true, and it reasons about what is worth doing, and it keeps the two clearly apart.
§ VI
run it
It ships with the baseline. There is nothing to install beyond the baseline itself.