How do I install the Spec Continue skill?

Run npx skillmds@latest add ainova-systems/spec-continue in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Spec Continue safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Spec Continue?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Spec Continue free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Spec Continue?

ainova-systems (@ainova-systems) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Spec Continue by ainova-systems — Agent Skill

Name: Spec Continue
Author: ainova-systems

File contents

Continue a Spec

Resume a spec started in another session. Read spec-execute first - all its phases and constraints apply verbatim; this skill adds only the resume protocol. The resume failure mode is always the same: inherited code drifts from the spec, and new work gets stacked on the drift.

Resume protocol

Read the spec end-to-end; find where work actually paused - from the last ticked work step and last commit, not from the top.
Rebuild repo state: git status, git log --oneline -20, git branch --show-current, gh pr list --head <branch>.
Triage uncommitted working-tree changes not made by this session: diff each file against the spec's target shape, not against the last commit. Aligned - absorb and say so. Divergent - present an A-vs-B choice (revert to spec shape vs fix in place); never silently absorb, never git restore someone's work without approval. Stage selectively (git add <file>), never git add -A on resume. In supervised mode an uncommitted tree is the expected end state of the previous run, not foreign work - check the ticked steps before treating it as drift.
Drain unacked PR feedback first (when a PR exists): gh pr checks <pr> + gh pr view <pr> --json reviews,comments, then git-complete-pr. Red lights before new work.
Reconcile the plan's ## Work steps vs reality: tick what shipped; a [x] whose gate does not re-run dry is a regression to investigate, and the investigation lands in ## Corrections.
Audit the inherited last commit for cross-cutting drift: removed symbol still called elsewhere; migration landed but consumers stale; hand-rolled component where a shared one exists; pattern invented where a sibling covers it. Any hit - the next work is a rescope to the spec, not a continuation.
Re-read the plan's MUST READ FIRST preamble and ## Open questions (a standing question stops the run, same as spec-execute); then continue per spec-execute Phase C verbatim.

Verify

Inherited work reconciled (absorbed, rescoped, or surfaced); PR feedback drained; next work step identified from the plan.

Scope / hand-off

Fresh execution - spec-execute; spec authoring - spec-pull / spec-create; open questions - spec-answer.

Constraints

Never assume the spec reflects reality - re-sync with the repo first.
Never delete or rewrite pushed work: fix-commit forward.
Branch behind its base - ask merge or rebase; never silently diverge.
"Reconcile with the spec's target shape" ranks above "tick the next checkbox".

---name: spec-continuedescription: Resumes an in-progress spec: audits inherited work for drift, then continues from the first unticked work step.---# Continue a SpecResume a spec started in another session. **Read `spec-execute` first - all its phases and constraints apply verbatim**; this skill adds only the resume protocol. The resume failure mode is always the same: inherited code drifts from the spec, and new work gets stacked on the drift.## Resume protocol1. Read the spec end-to-end; find where work actually paused - from the last ticked work step and last commit, not from the top.2. Rebuild repo state: `git status`, `git log --oneline -20`, `git branch --show-current`, `gh pr list --head <branch>`.3. Triage uncommitted working-tree changes not made by this session: diff each file against the spec's target shape, not against the last commit. Aligned - absorb and say so. Divergent - present an A-vs-B choice (revert to spec shape vs fix in place); never silently absorb, never `git restore` someone's work without approval. Stage selectively (`git add <file>`), never `git add -A` on resume. In `supervised` mode an uncommitted tree is the expected end state of the previous run, not foreign work - check the ticked steps before treating it as drift.4. Drain unacked PR feedback first (when a PR exists): `gh pr checks <pr>` + `gh pr view <pr> --json reviews,comments`, then `git-complete-pr`. Red lights before new work.5. Reconcile the plan's `## Work steps` vs reality: tick what shipped; a `[x]` whose gate does not re-run dry is a regression to investigate, and the investigation lands in `## Corrections`.6. Audit the inherited last commit for cross-cutting drift: removed symbol still called elsewhere; migration landed but consumers stale; hand-rolled component where a shared one exists; pattern invented where a sibling covers it. Any hit - the next work is a **rescope to the spec**, not a continuation.7. Re-read the plan's MUST READ FIRST preamble and `## Open questions` (a standing question stops the run, same as `spec-execute`); then continue per `spec-execute` Phase C verbatim.## Verify- Inherited work reconciled (absorbed, rescoped, or surfaced); PR feedback drained; next work step identified from the plan.## Scope / hand-off- Fresh execution - `spec-execute`; spec authoring - `spec-pull` / `spec-create`; open questions - `spec-answer`.## Constraints- Never assume the spec reflects reality - re-sync with the repo first.- Never delete or rewrite pushed work: fix-commit forward.- Branch behind its base - ask merge or rebase; never silently diverge.- "Reconcile with the spec's target shape" ranks above "tick the next checkbox".

Frequently asked questions

Spec Continue