@skitterbyte/skitterspec 14.0.3 → 15.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/assets/rules/spec-planning.md +9 -7
  2. package/package.json +1 -1
package/assets/rules/spec-planning.md CHANGED
@@ -68,13 +68,15 @@ Beneath it, `skitterspec spec-env live <take|release|abort|status>` is the engin
68
68
  tracker-free: it knows nothing about any specific ticketing system. A
69
69
  ticketing provider is installed as its own distribution that plugs into two named
70
70
  **seams** in the shared skills (`/spec` Phase E, `/spec-go` step 3b) and fulfils a
71
- skill-name + CLI contract — it ships `/spec-status` (read-only per-field
72
- divergence), `/spec-pull` (tracker→repo), and `/spec-push` (repo→tracker), backed
73
- by a `spec-sync` CLI, three-way merged against a committed base sidecar. When a
74
- provider is present, `/spec` also links the spec to the tracker and `/spec-go`
75
- pulls first. With no provider installed the seams are empty and every skill
76
- behaves as a plain filesystem workflow. See the provider package's own docs for
77
- its config and field reference.
71
+ skill-name + CLI contract. Sync is **one-way**: the repo is the source of truth
72
+ and the tracker is a **generated mirror**. It ships `/spec-push` (repo→tracker;
73
+ computes a create/update plan against a committed last-pushed snapshot and applies
74
+ it) and `/spec-status` (read-only drift report — what would push, and whether the
75
+ tracker's workflow-state drifted), backed by a `spec-sync` CLI. There is no
76
+ content pull — the tracker is never read back or merged. When a provider is
77
+ present, `/spec` also links the spec to the tracker. With no provider installed
78
+ the seams are empty and every skill behaves as a plain filesystem workflow. See
79
+ the provider package's own docs for its config and field reference.
78
80
 
79
81
  ## Project conventions (fill this in)
80
82
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@skitterbyte/skitterspec",
3
- "version": "14.0.3",
3
+ "version": "15.0.0",
4
4
  "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.",
5
5
  "keywords": [
6
6
  "claude",