next-steps

Generates a four-field closing block stating what landed, user actions, and the next command.

2|Updated Jul 24, 2026
One-click install
npx skills add https://github.com/konstantinos-malavazos/claude-code-playbook --skill next-steps-konstantinos-malavazos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: next-steps
Source: https://github.com/konstantinos-malavazos/claude-code-playbook/tree/main/templates/skills/next-steps
Command: npx skills add https://github.com/konstantinos-malavazos/claude-code-playbook --skill next-steps-konstantinos-malavazos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an AI-assisted workflow stage finishes, users are often left unsure what to do next — whether to commit, which command to run, or whether to start a fresh session. This Skill standardizes the final output of any flow so every ending hands the user a concrete next move. ## Core Features & Use Cases - Four-field hand-back block: Prints Landed (what was produced and where), Yours now (user-only actions), Next command (with the argument filled in), and This session or a fresh one (with a one-clause reason). - Terminal-point triggering: Auto-loads at any flow ending — a finished stage, a verdict, a report, or a stop-with-a-question — so no ending is left ambiguous. - Guardrail enforcement: Forbids placeholder arguments, non-existent commands, blanket commit advice, and any suggestion to merge or push to trunk. - Use Case: After a ticket pipeline stage finishes green, the flow prints the commit sha, states nothing is left for the user, and gives the literal next command like /cut-backlog with a note to run it in a fresh session. ## Quick Start Ask the assistant to end the current workflow stage with a next-steps block that states what landed, what you must do, and the exact next command to run.

Frequently Asked Questions about next-steps

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I end an AI workflow stage with clear next steps?

Print a four-field block after the stage report: Landed (output and its path or id), Yours now (user-only actions), Next command (with the argument filled in), and whether it runs in this session or a fresh one. The block follows the report and never replaces it.

What should a hand-back message include after an automated task?

A hand-back should state what landed and where, what only the user can do, the literal next command with its argument, and the session guidance with a one-clause reason. Fields with nothing to say must say so explicitly rather than being omitted.

Can the next-steps block suggest committing or pushing code?

Commit guidance must follow each stage's own rule — some stages commit when green, others commit nothing, and fixes amend. The block must never suggest merging or pushing to trunk, and push advice is limited by the repo allowlist.

When should the next command run in a fresh session?

A fresh session is recommended when the next unit of work is sized to a fresh context, such as one ticket per session. The block states this in one clause, for example noting that the current context is full of scaffolding.

What happens when a workflow stops with a question instead of a result?

A stop-with-a-question still gets a block: Yours now contains the question itself and Next command is none — answer here. This prevents the user and the agent from waiting on each other.