agentsclimarketplace
Sign in

Spec continue

Skill ainova-systems/intelligence-dev-packs/packs/spec/skills/spec-continue

Resume an in-progress spec: audit inherited work for drift, then continue executionFrom its SKILL.md

Install
npx -y skills add ainova-systems/intelligence-dev-packs --skill spec-continue

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
  • runs commandsInstructs the agent to run 8 commands, including `git status` and 7 more.

SKILL.md

2.3 KB, 515 tokens by cl100k_base, as published. Nobody here has run it

Continue a Spec

Resume a spec started in another session. Read spec-execute first - all its phases and CRITICAL rules 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

  1. Read the spec end-to-end; find where work actually paused - from the last tick/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.
  4. Drain unacked PR feedback first: gh pr checks <pr> + gh pr view <pr> --json reviews,comments, then git-review-pr-comments. Red lights before new work.
  5. Reconcile tasks.md vs real commits: tick what shipped; a [x] with no matching commit is a regression to investigate.
  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 commit is a rescope to the spec, not a continuation.
  7. Re-read the plan's MUST READ FIRST preamble; then continue per spec-execute Phase C verbatim.

Verify

  • Inherited work reconciled (absorbed, rescoped, or surfaced); PR feedback drained; next task identified from the spec.

Scope / hand-off

  • Fresh execution - spec-execute; spec authoring - spec-create.

CRITICAL

  • 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".

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.