kiro-next

Reports current spec workflow position and the exact next Kiro command.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/scapia-oss/compass --skill kiro-next-scapia-oss
Or copy as Structured Prompt for Agentâ–¼
Please help me install this Agent Skill.
Skill: kiro-next
Source: https://github.com/scapia-oss/compass/tree/main/tools/cc-sdd/templates/agents/claude-code-skills/skills/kiro-next
Command: npx skills add https://github.com/scapia-oss/compass --skill kiro-next-scapia-oss

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Engineers working through a spec-driven development workflow often lose track of where they are — which spec is active, what stage it is in, and which command to run next. This Skill removes that guesswork by running a deterministic status script and printing the evidence-backed next step. ## Core Features & Use Cases - Workflow Position Detection: Runs the kiro-status.mjs script to show exactly where you stand in the Kiro spec workflow. - Next Command Guidance: Prints the exact next command to run, sourced from the script output rather than guesswork. - Auto-Detection of Active Specs: When no feature name is given, it detects the most recent unfinished spec and lists candidates if multiple are active. - Use Case: You return to a project after a week and cannot remember whether you finished the design phase. Ask what is next, and the Skill tells you the pending stage and the exact command to continue. ## Quick Start Ask the assistant what is next in my Kiro workflow, optionally naming a specific feature to check its status.

Frequently Asked Questions about kiro-next

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

FAQPage Schema
How do I find the next step in a spec-driven workflow?â–¼

Run the kiro-next skill, which executes the kiro-status.mjs script to show your current workflow position and the exact next command. The script output is the source of truth, so no step is invented from memory.

How to check spec status without naming a feature?â–¼

Invoke the skill with no arguments and the script auto-detects the most recent unfinished spec. If multiple active candidates exist, it lists them so you can rerun with a specific feature name.

Does kiro-next modify my spec files or tasks?â–¼

No, the skill is strictly read-only. It does not edit spec.json, tasks, artifacts, or steering files; it only runs the status script and prints its output verbatim.

What happens when multiple specs are in progress?â–¼

The script keeps its candidate list visible and instructs you to run the next command with a specific feature name. This avoids guessing which spec you intended to continue.

Why does the skill refuse to suggest a command from memory?â–¼

Workflow state lives in version-controlled files, so only the deterministic status script can report it accurately. Inventing a next command from chat memory risks skipping gates or repeating completed stages.