@skitterbyte/skitterspec 16.6.0 → 16.7.0

package/assets/skills/spec-bug/SKILL.md

@@ -173,6 +173,13 @@ test, split the fix into phase files (`01-<slug>.md` …) with a phase index in
 `00-overview.md`, and leave the spec in `in-progress` for `/spec-go` to continue.
 Say so explicitly — don't fake green.
 
+**Then refresh the mirror (only if a provider is installed).** The Fix tasks are
+ticked, so the repo is now the truth about this fix — and this skill can take a
+bug all the way to green without `/spec-go` ever running. Without a provider this
+is a no-op.
+
+
+
 ## 6. Report
 
 Summarise: root cause, the failing→passing test, the fix, and the full test

package/assets/skills/spec-go/SKILL.md

@@ -139,20 +139,20 @@ Before writing any code for this phase, get the workspace clean:
   next phase on top of an uncommitted one. (Skip if this is the first phase —
   there's nothing prior to commit.)
 
-## 3b. Sync with the tracker (only if a provider is installed)
-
-**Only when a ticketing provider is installed** and the spec is linked to the
-tracker. Otherwise skip this step — no provider means zero change to the flow
-below. Follow the provider's steps below (nothing to do here without one).
-
-
-
 ## 4. Implement the phase
 
 Identify the **first unfinished phase** from the `00-overview.md` phase index,
 then open its phase file (`0N-<slug>.md`) — that file holds the tasks. Mark it
 started: set the phase-file heading to `🔄` and its `> **Status:**` to
 `In progress`, and flip the matching row in the overview phase index to `🔄`.
+
+**Then sync with the tracker (only if a provider is installed).** The phase has
+just changed state, so refresh the mirror before the build starts — that is what
+makes the phase show as in progress *while* it is being built rather than only
+once it is over. Without a provider this is a no-op and nothing below changes.
+
+
+
 Then build it, following the project rules in `.claude/rules/*.md` and `CLAUDE.md`:
 
 - Work task by task through the phase file. Make focused edits that match
@@ -175,6 +175,12 @@ Then build it, following the project rules in `.claude/rules/*.md` and `CLAUDE.m
 - If new work surfaced, add it as tasks to the appropriate phase file (or add a
   new phase file + index row) rather than doing it silently.
 
+**Then refresh the mirror (only if a provider is installed).** The phase is done
+in the repo now; leaving the tracker to catch up at `/spec-complete` is what makes
+a mirror lag a whole spec behind. Without a provider this is a no-op.
+
+
+
 ## 6. Report
 
 Summarise what was implemented, the test result (quote failures if any), and

package/assets/skills/spec-hotfix/SKILL.md

@@ -180,6 +180,13 @@ narrative and decisions).
 - Commit the fix to the `hotfix/<slug>` branch (this commit is what gets tagged
   and cherry-picked). Tick the Fix tasks; add a Changelog line.
 
+**Then refresh the mirror (only if a provider is installed).** The Fix tasks are
+ticked, so the repo is now the truth about this fix — and this skill can take a
+bug all the way to green without `/spec-go` ever running. Without a provider this
+is a no-op.
+
+
+
 ## 7. Report
 
 Summarise: the base tag, root cause, the failing→passing test, the fix, and the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@skitterbyte/skitterspec",
-  "version": "16.6.0",
+  "version": "16.7.0",
   "description": "Spec-driven development for Claude Code — a tracker-free filesystem workflow: lifecycle skills and per-spec isolation. For Linear sync, install @skitterbyte/skitterspec-linear instead.",
   "keywords": [
     "claude",