sp-auto

What problem does it solve? When working through a Spec Kit Plus workflow, it is easy to lose track of which command should run next, especially across features, quick tasks, debug sessions, and discussion handoffs. This Skill reads the repository's authoritative workflow state files and resumes the correct next step automatically, so you never have to guess or manually name the exact command. ## Core Features & Use Cases - State-driven routing: Inspects workflow-state.md, implement-tracker.md, human-acceptance.json, quick-task STATUS files, debug sessions, and discussion handoff state in priority order to select exactly one safe canonical next command. - Faithful continuation: Executes the routed command under its own full contract, preserving canonical next_command tokens and artifact semantics rather than blending workflows. - Safe diagnostics: When state is missing, stale, or conflicting, it stops in read-only mode and reports the exact blocker plus the repair or canonical command needed to unblock. - Use Case: You return to a spec-kit project after a break and cannot remember whether you finished planning or task generation. Invoke the auto entrypoint and it reads the feature's workflow state, routes to /sp.tasks or /sp.implement as recorded, and continues that workflow. ## Quick Start Ask the agent to continue my Spec Kit Plus workflow from wherever the repository state says I left off.