next-stepslisted
Install: claude install-skill konstantinos-malavazos/claude-code-playbook
# Next steps — end by saying what the human does now
Every flow knows precisely when it is finished. A **stop condition** says what you must not
do next, and a **report** says what landed. Neither of those is a next step. This block is.
**It is the last thing printed, and it never replaces the stage's own report** — it follows
it. If it is restating the report above it, it is too long.
---
## The four fields, in this order
| Field | What it carries |
|---|---|
| **Landed** | one line: what this stage produced, and where it is — branch and sha, ticket ids, file paths. Never an artifact without its path or id |
| **Yours now** | only what the user must do, because only they can: commit, push, open the MR/PR, approve the board, send the questionnaire, run the wizard, restart the session |
| **Next command** | the literal command with the argument **filled in** — `/charting 7`, `/start-ticket ABC-123`, `/resume-massive PLATFORM` |
| **This session or a fresh one** | stated outright, with the one-clause reason |
```
**Landed** — <what this stage produced, and where it is>
**Yours now** — <only what they must do, because only they can>
**Next command** — `/<command> <argument, filled in>`
**This session or a fresh one** — <which, and why, in one clause>
```
**A field with nothing to say says so** — *nothing to commit*, *nothing to run*, *none, this
one is over* — and never disappears. An ending with a field missing reads as an unfinished
conversation, which is the thing this