speckit-companion-resume

Resumes spec-driven pipelines by dispatching the next speckit command from recorded state.

1|Updated Nov 21, 2020
One-click install
npx skills add https://github.com/LuanDopke/persefone --skill speckit-companion-resume-luandopke
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-companion-resume
Source: https://github.com/LuanDopke/persefone/tree/main/.agents/skills/speckit-companion-resume
Command: npx skills add https://github.com/LuanDopke/persefone --skill speckit-companion-resume-luandopke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working through a multi-step spec-driven development pipeline, it is easy to lose track of which step was completed last and which decisions were already recorded. This Skill reads the active feature's state and picks the pipeline back up exactly where it stopped, so prior decisions carry forward without re-specification. ## Core Features & Use Cases - State Resolution: Runs a status-context script that reads .spec-context.json or derives state from on-disk spec files when the recorded state is missing or malformed. - Next-Step Dispatch: Parses the resolution JSON and dispatches the appropriate /speckit.* command (plan, tasks, implement), or continues implementation at the next unchecked task. - Decision Carry-Forward: Restates recorded decisions as in-scope context for the dispatched step so the user does not repeat them. - Use Case: You finished /speckit.plan yesterday and return today. Invoke the resume command and it detects the plan step is complete, lists the recorded decisions, and dispatches /speckit.tasks automatically. ## Quick Start Ask the assistant to resume the spec pipeline for the current feature so it continues from the last completed step.

Frequently Asked Questions about speckit-companion-resume

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

FAQPage Schema
How do I resume a spec-kit pipeline after stopping mid-workflow?▼

Invoke the resume command, which runs the status-context script to read the feature's recorded state. It then dispatches the next speckit command, such as plan, tasks, or implement, based on the last completed step.

How does spec-kit resume handle recorded decisions from earlier steps?▼

The resolution output includes a decisions array that the resume command restates as in-scope context when dispatching the next step. This ensures prior choices carry forward without the user re-specifying them.

Does resume work if the .spec-context.json state file is missing?▼

Yes. The status-context script derives the pipeline state from on-disk spec files when the recorded state file is missing or malformed, so resume still resolves the correct next step.

What happens when I resume a spec pipeline that is already complete?▼

When the resolution reports complete as true, the command prints a pipeline-complete message and stops without dispatching anything. It never re-runs finished steps.

Why does resume skip when python3 is not installed?▼

The status resolution depends on a Python script, so the command checks for python3 first. If it is unavailable, resume prints a warning and stops gracefully without failing the host command.