Name: Next
Author: iamalisson

ASecurity

Show a spec-kit feature's progress (a task is done when its issue is closed) and start the next open task with /speckit-implement; with several features, asks which. Use when the user asks what's next or has just merged a task PR.

2 stars
0 votes
0 copies
0 views
Added November 5, 2026

developmentbashsecurity

Security analysis

A100/100

Scanned November 5, 2026

npx -y skills add iamalisson/jit-speckit --skill next --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Next?

Add the live security badge to your README. It updates with every re-scan.

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/iamalisson-next/badge)](https://www.skillsdirectory.com/skills/iamalisson-next)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: next
description: "Show a spec-kit feature's progress (a task is done when its issue is closed) and start the next open task with /speckit-implement; with several features, asks which. Use when the user asks what's next or has just merged a task PR."
argument-hint: "[feature]"
---

# Next task

1. Run `bash .specify/extensions/jit/scripts/next.sh [feature]`, with the argument when the user
   named a feature (`002` or `002-reports`); it becomes the active feature.
   - If `.specify/extensions/jit/` does not exist, tell the user to run `/jit-speckit:init`
     first, and stop.
   - If it prints `CHOOSE=...`, more than one feature has tasks to start: show the `feature` lines
     with their counts, ask which one, and run it again with that feature.
2. Show the progress as a short list (done / resume / in-progress / blocked / open / no-issue),
   then `DONE=x/y`.
   - **blocked** tasks say "depends on Txxx" on their line and that task's issue is still open;
     they are never picked before it closes (merge that PR first).
   - **resume** is a task whose branch you started in this clone; it is picked first.
   - **in-progress** tasks are being done elsewhere (a branch on origin, another worktree, an
     open PR) and are never picked; they finish when their PR merges.
   - If tasks have **no issue**, say so and suggest `/speckit-jit-issues`.
   - If `NEXT` is empty and `IN_PROGRESS` is not 0, nothing is left to start: list the open PRs
     to merge, and stop.
   - If `NEXT` is empty and `IN_PROGRESS=0`, every task's issue is closed. Before calling the feature done, suggest
     `/speckit-converge`: it compares the merged code with the spec and adds any unbuilt work as
     new tasks, which then get their own issues. If it finds nothing, the feature is complete:
     suggest `/jit-speckit:security` before the next release, and `/speckit-specify` for the
     next feature. Stop.
3. Make sure the working tree is clean. If it isn't, stop and say so; never stash or discard.
4. Run `/speckit-implement <NEXT>`. It switches to the task's branch, implements it, runs the
   pre-PR checks and opens the PR.