@skitterbyte/skitterspec 14.0.1 → 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.
|
@@ -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
|
|
72
|
-
|
|
73
|
-
|
|
74
|
-
|
|
75
|
-
|
|
76
|
-
|
|
77
|
-
|
|
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
|
|
|
@@ -190,3 +192,7 @@ queried directly.)
|
|
|
190
192
|
- Never delete historical notes.
|
|
191
193
|
- The spec file is the single source of truth for implementation progress.
|
|
192
194
|
- Move specs between buckets with `git mv` to preserve history.
|
|
195
|
+
- Never let inline emphasis or a link cross a hard line break — keep a whole
|
|
196
|
+
`**bold**`, `*italic*`, or `[text](url)` on one line (let it overflow the wrap
|
|
197
|
+
column rather than splitting it). Many round-tripping editors mangle a
|
|
198
|
+
`**`/`*`/link span that straddles a newline, so clean source avoids the churn.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@skitterbyte/skitterspec",
|
|
3
|
-
"version": "
|
|
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",
|