@skitterbyte/skitterspec-jira 2.2.0 → 2.3.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.
@@ -635,6 +635,56 @@ its phases. It carries `> **Severity:**` (Azure's literal values,
635
635
  unfolds; `/spec-complete` writes `incident-log.md` from it and pushes the log
636
636
  onto the tracker item as a comment.
637
637
 
638
+ ### Kind routing — any door, the right spec
639
+
640
+ `/spec` is the default door, so the kind of work someone describes does not
641
+ always match the skill they typed — especially for someone new, for whom
642
+ "spec it" is the reflex. Every entry skill therefore
643
+ **watches its grill for the signals that mark the other kinds**, and proposes a
644
+ hand-off the moment one appears — never at the end of a grill already shaping
645
+ the wrong spec:
646
+
647
+ | In | Watches for | Hands to |
648
+ |----|-------------|----------|
649
+ | `/spec` | defect · defect on a released version · live outage | `/spec-bug` · `/spec-hotfix` · `/spec-incident` |
650
+ | `/spec-bug` | on a released version · live outage · not a defect | `/spec-hotfix` · `/spec-incident` · `/spec` |
651
+ | `/spec-hotfix` | live outage · not on a released version · not a defect | `/spec-incident` · `/spec-bug` · `/spec` |
652
+ | `/spec-incident` | no live outage to record | defect → `/spec-bug` (on a released version → `/spec-hotfix`), else `/spec` |
653
+
654
+ Feature, chore and issue all route to `/spec` — one door for the three kinds it
655
+ writes, where its kind proposal picks between them. Example signals, weighed in
656
+ context rather than matched as keywords: a **defect** is behaviour differing
657
+ from intended — "it's broken", a failing flow, a stack trace of a failure;
658
+ **on a released version** is that defect where what is deployed is named — "in
659
+ prod", "since v2.1"; a **live outage** is a service down or degraded
660
+ **right now**, users affected as we speak; **not a defect** is an ask for new or
661
+ changed behaviour rather than for restoring intended behaviour.
662
+
663
+ Three rules, the same in every skill:
664
+
665
+ - **Always confirm; never silently switch.** Name the signal in the user's own
666
+ words and propose the destination with a one-line reason; the user confirms
667
+ or declines. A decline ends the matter — the grill carries on where it was,
668
+ and the same signal is not raised again. A signal is a question, never a
669
+ verdict: a pasted stack trace in "handle this error nicely" is a feature
670
+ request, not a bug report.
671
+ - **Precedence: incident > hotfix > bug.** One description can carry several
672
+ signals; propose the most specific destination — the same reasoning the
673
+ intake label routing documents for hotfix-over-bug.
674
+ - **Hand off in-session, carrying the context.** On a confirmed switch the
675
+ current skill invokes the destination skill directly and seeds it with
676
+ everything the grilling has already established — symptom, version, impact,
677
+ repro material, decisions so far — so the destination grills only what it
678
+ still needs ("seed, don't skip, the grill", the principle issue adoption
679
+ already uses). Stop-and-retype is the **label** routing's shape, and right
680
+ there because it fires before any grilling; mid-grill it would throw away
681
+ the answers already given.
682
+
683
+ This is judgment, not configuration: the signals are examples, there is no
684
+ list to maintain, and nothing here reads a label. A ticketing provider's
685
+ intake label routing (`intake.bugLabels` / `intake.hotfixLabels`) is a
686
+ separate, earlier check and is unchanged by this.
687
+
638
688
  All six types share the same lifecycle folders below — type is orthogonal to
639
689
  status.
640
690
 
@@ -188,6 +188,39 @@ not write the spec until this is resolved.
188
188
  Stop grilling when there are no unresolved branches that would change the spec.
189
189
  Briefly play back the agreed understanding before writing.
190
190
 
191
+ ### Watch for the other doors — bug, hotfix, incident
192
+
193
+ `/spec` is the default door, so work that belongs to another skill arrives here
194
+ described in the user's own words — no issue, no labels for Phase 0 to route
195
+ on. While grilling, watch for the signals that mark the other kinds and raise
196
+ the hand-off **the moment one appears**, not at the end of the grill: for a
197
+ live outage especially, finishing a feature grill first is actively harmful,
198
+ because `/spec-incident` exists to be written *during* the outage.
199
+
200
+ - **Defect** — behaviour differing from intended ("it's broken", a failing
201
+ flow, a stack trace of a failure) → propose **`/spec-bug`**.
202
+ - **Defect on a released version** — the defect is on what is deployed ("in
203
+ prod", "since v2.1") → propose **`/spec-hotfix`**.
204
+ - **Live outage** — a service down or degraded **right now**, users affected
205
+ as we speak → propose **`/spec-incident`**.
206
+
207
+ **Always confirm; never silently switch.** Name the signal in the user's own
208
+ words, propose the destination with a one-line reason, and let them decide. A
209
+ decline carries the grill on where it was, and the same signal is not raised
210
+ again. A signal is a question, never a verdict: a pasted stack trace in
211
+ "handle this error nicely" is a feature request. When one description carries
212
+ several signals, propose the most specific destination —
213
+ **incident > hotfix > bug**.
214
+
215
+ **On a confirmed switch, hand off in-session and carry the context.** Invoke
216
+ the destination skill directly and seed it with everything the grilling has
217
+ already established — symptom, version, impact, repro material, decisions so
218
+ far — so it grills only what it still needs ("seed, don't skip, the grill",
219
+ exactly as issue adoption does). Do not stop and tell the user to retype: that
220
+ shape belongs to Phase 0's label routing, which fires before any grilling has
221
+ happened and so has nothing to lose. The full routing matrix lives in
222
+ `.claude/rules/spec-planning.md`.
223
+
191
224
  ### Propose the kind — feature, chore or issue
192
225
 
193
226
  This skill writes three kinds of spec, and
@@ -215,10 +248,13 @@ the point.
215
248
 
216
249
  There is no `/spec-chore` or `/spec-issue` and none should be added: one entry
217
250
  point, one grill, and the kind is an output of understanding the work rather
218
- than a door the user must pick before describing it. The one kind with its own
219
- door is the **incident** — an outage or degradation of a live service, which
220
- needs a different grill and starts mid-flight — so when the grilling uncovers
221
- one, hand off to **`/spec-incident`** rather than writing it here.
251
+ than a door the user must pick before describing it. The kinds with their own
252
+ doors — bug, hotfix, and the **incident**, an outage or degradation of a live
253
+ service that needs a different grill and starts mid-flight — are the watch's
254
+ business above: when the grilling uncovers one, hand off to **`/spec-bug`**,
255
+ **`/spec-hotfix`** or **`/spec-incident`** rather than writing it here, and it
256
+ is never too late to propose that — reaching this proposal with the signal
257
+ unraised is a missed watch, not a reason to write the wrong kind.
222
258
 
223
259
  ## Phase B — write the spec
224
260
 
@@ -150,6 +150,38 @@ Bugs are concrete — confirm, don't over-grill. Establish:
150
150
  against the broken one (the bug usually lives in the differential). Do NOT
151
151
  patch a symptom before you understand the cause.
152
152
 
153
+ ### Watch for the other doors — hotfix, incident, or not a bug at all
154
+
155
+ The investigation above is where mis-entry shows, so watch it for the signals
156
+ that mark the other kinds and raise the hand-off the moment one appears —
157
+ before the failing test is written, while nothing is on disk
158
+ (`.claude/rules/spec-planning.md` carries the full routing matrix):
159
+
160
+ - **On a released version** — the defect is on what is deployed ("in prod",
161
+ "since v2.1") → propose **`/spec-hotfix`**. This is the escalation that must
162
+ not be missed: a fix built here lands on `main` and never reaches the
163
+ running version.
164
+ - **Live outage** — a service down or degraded **right now** → propose
165
+ **`/spec-incident`**; the record comes first, and the fix returns as a
166
+ linked spec.
167
+ - **Not a defect** — the ask is new or changed behaviour, not restoring
168
+ intended behaviour → propose **`/spec`**, whose kind proposal picks feature,
169
+ chore or issue from there.
170
+
171
+ **Always confirm; never silently switch** — name the signal in the user's own
172
+ words with a one-line reason, and a decline carries this skill on where it
173
+ was, the same signal not raised again. When several signals appear at once,
174
+ propose the most specific destination — incident over hotfix.
175
+ **On a confirmed switch, hand off in-session and carry the context**: invoke
176
+ the destination skill directly and seed it with what §1 established — symptom,
177
+ repro, root-cause notes, any version named — so it grills only what it still
178
+ needs.
179
+
180
+ **Once the failing test exists, the repro is evidence, not a question to re-litigate**
181
+ — but evidence can still escalate: a red test that also fails at
182
+ the released tag is the hotfix signal with proof attached, and the hand-off
183
+ carries the failing test across.
184
+
153
185
  ## 2. Isolate the fix in a worktree — when isolation is enabled
154
186
 
155
187
  **Only when per-spec isolation is enabled** (`specs/.core/env.config.json`
@@ -177,6 +177,27 @@ Hotfixes are concrete — confirm, don't over-grill. Establish:
177
177
  - **Root cause:** read the code **at the base tag** and trace it to `file:line`.
178
178
  The fix belongs on the tag's line, so reason about that code, not `main`'s.
179
179
 
180
+ ### Watch for the other doors — incident, bug, or not a defect
181
+
182
+ This is the most specific defect door, so most mis-entries route *down*
183
+ (`.claude/rules/spec-planning.md` carries the full routing matrix):
184
+
185
+ - **Live outage** — the released version is not just wrong but down or
186
+ degraded **right now** → propose **`/spec-incident`**; the record comes
187
+ first, and the fix returns here as a linked hotfix spec.
188
+ - **Not on a released version** — §1 cannot name a deployed tag the defect is
189
+ on (it exists only on `main`, or prod runs something newer that is fine) →
190
+ propose **`/spec-bug`**; a hotfix branch for something `main` can carry is
191
+ waste, not safety.
192
+ - **Not a defect** — the ask is new or changed behaviour, not restoring
193
+ intended behaviour → propose **`/spec`**.
194
+
195
+ **Always confirm; never silently switch** — name the signal in the user's own
196
+ words with a one-line reason; a decline carries this skill on where it was.
197
+ **On a confirmed switch, hand off in-session and carry the context**
198
+ established so far — the symptom, the repro, any version discussion — so the
199
+ destination grills only what it still needs.
200
+
180
201
  ## 3. Provision the worktree from the tag, then write in it
181
202
 
182
203
  **Provision before you write, not after.** §1 settled the tag and the name and
@@ -37,6 +37,28 @@ Ask for exactly these, batched, with nothing speculative:
37
37
  A root cause is **not** grilled: nobody has it yet, and the Timeline is where
38
38
  the investigation lands as it happens.
39
39
 
40
+ ### No live outage to record — route to the right door
41
+
42
+ This is the costliest door to enter wrongly — no backlog stop, no review page,
43
+ straight into `specs/in-progress/` — so the grill's own answers are also its
44
+ exit. When items 1 and 2 establish there is **no outage to record** — nothing
45
+ is down or degraded, it never was live, or it is a risk rather than an event —
46
+ propose the right door instead of writing an incident
47
+ (`.claude/rules/spec-planning.md` carries the full routing matrix):
48
+
49
+ - a **defect** → **`/spec-bug`**, or **`/spec-hotfix`** when it is on a
50
+ released version;
51
+ - anything else → **`/spec`**, whose kind proposal picks feature, chore or
52
+ issue from there.
53
+
54
+ **A past outage someone wants a record of stays an incident**: "it is over" is
55
+ not "it never happened" — the signal is *no outage to record*, not *no outage
56
+ now*. This check is the grill's existing questions read honestly, never an
57
+ extra round trip, and the hand-off contract is the same as everywhere else:
58
+ confirm first, naming the signal in the user's own words; a decline carries
59
+ this skill on; on a confirmed switch invoke the destination skill in-session,
60
+ seeded with everything already established.
61
+
40
62
  ## 2. Write it, in flight
41
63
 
42
64
  Pick a short kebab name prefixed `incident-` (e.g. `incident-api-outage`).
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@skitterbyte/skitterspec-jira",
3
- "version": "2.2.0",
3
+ "version": "2.3.0",
4
4
  "description": "Spec-driven development for Claude Code, with one-way Jira Cloud sync — a superset of @skitterbyte/skitterspec: the base filesystem workflow plus /spec-status · /spec-push and the spec-sync CLI. The repo is canonical; Jira is a generated mirror. Install this OR the base OR the Linear superset — exactly one.",
5
5
  "keywords": [
6
6
  "claude",