Next

---
name: next
description: "Advance an SDLC change to its next step in the AI-native lifecycle (intent, spec, plan, build, verify, review, release, archive). Use when the user says \"continue\", \"next step\", \"what's next\", or wants to move a change forward without naming the stage."
when_to_use: The user says continue, asks what is next, or wants to start a ready backlog item.
argument-hint: "[change-id]"
license: "PolyForm-Noncommercial-1.0.0 with sdlc Additional Permissions, or sdlc Commercial License (https://github.com/marin-ai-tech/sdlc)"
compatibility: Requires the sdlc CLI (sdlc) from the sdlc package.
allowed-tools: Bash(sdlc *)
metadata:
  author: marin-ai technologies
  version: "1"
  generatedBy: "sdlc 0.23.7"
---

Advance a change to its next step in the SDLC.

!`sdlc next --json`
If the output above is missing, run `sdlc next --json`.

**Harness contract** (applies to every SDLC workflow)
- `sdlc` is the source of truth for lifecycle state. Read it (`sdlc status --change <id> --json`) instead of inferring the stage from the conversation, and re-read artifacts from disk before using them.
- Gates are human decisions. Never run `sdlc approve`, `sdlc reject`, `sdlc waive` or `sdlc tests unlock`, and never edit `.sdlc.yaml`. When a gate needs a person, stop, name the people from the hint (`next.people` in `sdlc next --json`) rather than the role, and give them the exact command to run in their own terminal.
- An answer in chat is never an approval: gate approvals, `track set`, `backlog move`/`drop` and other human decisions happen only as a command the person runs in their own terminal. Offer the choice, explain the consequences, and give the exact command.
- OpenSpec is the specification subsystem: `sdlc openspec <args>` runs the bundled OpenSpec CLI (`list --specs`, `show`, `validate`, `instructions`). Change folders live in `openspec/changes/<id>/`.
- **Change selection**: use the change named in the input. Otherwise run `sdlc status --json`; with exactly one active change use it, with several ask which one. Announce "Using change: <id>".
- **Language**: talk to the person, and write notes and artifacts, in the person's language; when `locale:` is set in `openspec/sdlc.yaml`, use that language. Keep command names, file names, ids and the template headings as they are (sdlc and OpenSpec parse those headings).
- End every workflow with the next step from `sdlc next --json` (the exact command when a person must act).

**Input**: the user's request (a change id, or a description of the work)

**Steps**

1. Select the change (see Change selection). If none is active, run `sdlc next --json`.
2. Run `sdlc next --change <id> --json` for an active change. It returns the derived `stage` and `next`.
3. If ready backlog items are available, use the AskUserQuestion tool with 2-4 choices and a recommended item. If `next.action` is `start-backlog-item`, run `sdlc backlog start <id>` using `next.item`, then continue with intent.
4. If `next.actor` is `human`: stop. Summarize what the person must review (the artifacts or evidence listed by `sdlc status --change <id>`), then give the exact `next.cli` command for them to run in their own terminal. Do not start work that the gate protects.
5. If `next.actor` is `agent`: run the workflow named by `next.workflow` - load the ``sdlc:<workflow>`` skill (or follow `/sdlc:<workflow>`) and carry out its steps for this change.
6. If `next.actor` is `none`: report that the change is archived or complete.

**Output**: the stage, what was done, and the next step (with the exact command when a person must act).

<!--
Generated by sdlc 0.23.7 (https://github.com/marin-ai-tech/sdlc).
Required Notice: Copyright (c) 2026 marin-ai technologies (https://github.com/marin-ai-tech/sdlc)
License: PolyForm Noncommercial 1.0.0 (https://polyformproject.org/licenses/noncommercial/1.0.0) with the sdlc Additional Permissions, or a commercial license; see https://github.com/marin-ai-tech/sdlc
-->