@skitterbyte/skitterspec-jira 2.6.0 → 2.8.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.
@@ -0,0 +1,21 @@
1
+ ---
2
+ description: What every member of an epic needs next, in which tab, and the epic page — bare uses the epic or member worktree you are in
3
+ argument-hint: "[<epic>]"
4
+ allowed-tools: Bash({{exec}} skitterspec epic status:*)
5
+ disable-model-invocation: true
6
+ ---
7
+ !`{{exec}} skitterspec epic status $ARGUMENTS`
8
+
9
+ Relay the engine output above verbatim. Add nothing and run nothing else.
10
+
11
+ **It is for coming back to the epic's tab.** Each member is built in a tab of
12
+ its own; this one is where you return to see what each needs. On a phone the
13
+ in-app browser closes to switch tabs, so the epic page's link is what you came
14
+ back for — it is the last thing printed.
15
+
16
+ **It reads, and nothing more.** It starts no server, claims no pass and runs no
17
+ member's next command: those are typed in that member's own tab. A waiting pass
18
+ it names is picked up there with `/spec-reviewed`.
19
+
20
+ **Only you can run it**, for `/spec-connect`'s reason: there is no judgement to
21
+ apply, so no model turn is spent finding one.
@@ -49,6 +49,7 @@
49
49
  "allowRemote": false,
50
50
  "commitWith": "/commit",
51
51
  "required": true,
52
+ "projectName": "",
52
53
  "reviewers": []
53
54
  },
54
55
  "live": {
@@ -329,11 +329,15 @@ through to a documented conservative default; see the field notes below.
329
329
  // draft: mid-spec PRs open as drafts (a draft cannot be merged, so
330
330
  // nothing downstream can close a ticket early); /spec-complete is
331
331
  // what flips the PR to ready. Default true.
332
- // specDocs: where a SPEC DOCUMENT lands under "pr". "trunk" (default) keeps
333
- // today's authoring land — needs direct push for docs. "branch"
334
- // has the spec ride the feature branch and land with the work's
335
- // PR; the backlog is then found via the tracker listing, and the
336
- // authoring worktree stays (it is the document's only copy).
332
+ // specDocs: where a SPEC DOCUMENT lands. "trunk" keeps the authoring land
333
+ // — needs direct push for docs under "pr". "branch" has the spec
334
+ // ride its feature branch and land with the work; the backlog is
335
+ // then found via the tracker listing, and the authoring worktree
336
+ // stays (it is the document's only copy). Default "trunk" —
337
+ // unless a ticketing provider is configured (its config file in
338
+ // specs/.core/) and this key is unset, under either strategy:
339
+ // then "branch", because the tracker already is the backlog.
340
+ // Setting the key, to either value, always wins.
337
341
  // The merged-check and PR commands need the host's CLI — `gh` on github.com,
338
342
  // `az` on dev.azure.com — detected from the remote URL, never configured. An
339
343
  // unknown host (Enterprise/Server domains included) degrades to the ancestry
@@ -564,6 +568,12 @@ through to a documented conservative default; see the field notes below.
564
568
  // because a commit made under rules nobody configured must not read as one
565
569
  // made under /commit.
566
570
  //
571
+ // `projectName` is what every generated page — the review page, the served
572
+ // index, the epic page — calls this project, in its tab and above its
573
+ // heading. Empty (the default) means the project folder's name in the
574
+ // primary checkout, never a worktree's; set it when that folder is called
575
+ // something like `app`. Default: "".
576
+ //
567
577
  // THERE IS NO OFF SWITCH. `"none"` existed and was removed: it produced a
568
578
  // verdict that records itself and does nothing, which is the one thing a
569
579
  // review page must not offer — a review is the guard in front of an action.
@@ -657,6 +667,7 @@ through to a documented conservative default; see the field notes below.
657
667
  "serve": "always",
658
668
  "commitWith": "/commit",
659
669
  "required": true,
670
+ "projectName": "",
660
671
  "reviewers": []
661
672
  }
662
673
  }
@@ -120,6 +120,7 @@ body {
120
120
 
121
121
  header { margin-bottom: 1rem; }
122
122
  h1 { font-size: 1.3rem; margin: 0 0 .3rem; overflow-wrap: anywhere; }
123
+ .eyebrow { color: var(--muted); font-size: .8rem; margin: 0 0 .15rem; overflow-wrap: anywhere; }
123
124
  .sub { color: var(--muted); font-size: .85rem; margin: 0; overflow-wrap: anywhere; }
124
125
  .sub .sep { opacity: .5; padding: 0 .35rem; }
125
126
  .a { color: var(--add-mark); }
@@ -833,6 +834,7 @@ a.ticket:hover { border-color: var(--accent); }
833
834
  <body>
834
835
  <div class="wrap" id="wrap">
835
836
  <header>
837
+ <p class="eyebrow" id="project" hidden></p>
836
838
  <h1 id="title"></h1>
837
839
  <p class="sub" id="sub"></p>
838
840
  <div class="controls">
@@ -3311,6 +3313,13 @@ a.ticket:hover { border-color: var(--accent); }
3311
3313
  // --- header --------------------------------------------------------------
3312
3314
  var titleEl = document.getElementById('title')
3313
3315
  titleEl.textContent = data.title
3316
+ // The project this page belongs to, above the heading. textContent, never
3317
+ // markup: the name comes from a config file and the page is served.
3318
+ if (data.project) {
3319
+ var projectEl = document.getElementById('project')
3320
+ projectEl.textContent = data.project
3321
+ projectEl.hidden = false
3322
+ }
3314
3323
  /**
3315
3324
  * The tracker ticket, beside the title and linked where there is a url.
3316
3325
  *
@@ -124,6 +124,14 @@ skip — never a flag. Putting the flag on `/commit` was the other suggestion an
124
124
  is worse: `/commit` belongs to skittership, which is why the gate is enforced
125
125
  by a hook rather than by editing that skill.
126
126
 
127
+ **`/epic` is the sixth command**, and it is user-only for the mild reason: it
128
+ pre-executes `skitterspec epic status` and relays it, so there is no judgement
129
+ to apply. It exists for the tab an epic is run from — each member is built in
130
+ a tab of its own, and on a phone the in-app browser has to close to switch
131
+ tabs, so the epic page's link has to be one command away rather than scrolled
132
+ past. Bare, it means the epic of the worktree it runs in. It reads and nothing
133
+ more: the next action it names for a member is typed in that member's tab.
134
+
127
135
  **A refusal may OFFER its own exit, and that is a different thing again.**
128
136
  Where the engine declares one, a skill relays the refusal and **then** offers it
129
137
  — once per obligation, with the choice recorded, and answered by the operator
@@ -237,15 +245,18 @@ worktree: `Commit & Start` keeps it and carries into `/spec-start`, plain
237
245
  `commit` tears it down, because a spec parked in the backlog should hold no
238
246
  checkout.
239
247
 
240
- **`land.specDocs: "branch"` is the exception, taken deliberately.** Where the
241
- base branch accepts no direct push even for documents, the spec rides its
242
- feature branch and lands with the work's PR: both verdicts commit and skip the
243
- integrate, plain `commit` keeps branch and worktree (they are the document's
244
- only copy), and the backlog is found through the tracker listing rather than
245
- `ls specs/backlog/` on base — the known branch-relative-bucket cost, accepted
246
- because the alternative is a spec that cannot be written at all. The worktree
247
- fork-point check is exempt in this mode for the hotfix's reason: the spec is
248
- *supposed* to be absent from the fork point.
248
+ **`land.specDocs: "branch"` is the exception — and the default with a tracker.**
249
+ The spec rides its feature branch and lands with the work: both verdicts commit
250
+ and skip the integrate, plain `commit` keeps branch and worktree (they are the
251
+ document's only copy), and the backlog is found through the tracker listing
252
+ rather than `ls specs/backlog/` on base. It began as the lane for a base branch
253
+ that accepts no direct push even for documents. It is now also what a project
254
+ gets by default once a ticketing provider is configured and the key is unset,
255
+ under either landing strategy: the ticket already exists and the board already
256
+ owns status, so a land whose only purpose was findability buys nothing. Setting
257
+ the key, to either value, always wins. The worktree fork-point check is exempt
258
+ in this mode for the hotfix's reason: the spec is *supposed* to be absent from
259
+ the fork point.
249
260
 
250
261
  **What this bought is the reason it changed.** The page waits for a verdict
251
262
  without a timeout — deliberately, because a reader walking away from a diff is
@@ -721,8 +732,26 @@ its order onto its members: rename the folder to `epic-<name>` (`git mv`), set
721
732
  `> **Type:** Epic`, add `> **Epic:**` and `> **Waits on:**` to each member (and
722
733
  a phase file's own `Waits on:` for a phase-level sync point), and delete the
723
734
  wave phase files — `epic status` derives them. Keep the plan's Decisions: they
724
- are the *why* the members' headers cannot say. Then check that
725
- `skitterspec epic status <epic>` reproduces the plan you had.
735
+ are the *why* the members' headers cannot say.
736
+
737
+ **A phase that is not a wave becomes a member.** A test pass, a review, a
738
+ manual step the plan held as a phase is its own spec of the kind its work is —
739
+ usually an **Issue** (manual steps, no code) — with `> **Epic:**` and its own
740
+ `> **Waits on:**`; whatever waited on that phase waits on the member instead.
741
+ An epic holds no phases, because it holds no check it cannot observe.
742
+
743
+ **Do it off the base branch, and check it before it lands.** The conversion is
744
+ documents only, so it is a `/no-spec` branch. From that worktree,
745
+ `skitterspec epic status <epic> --here` reads the members and headers as the
746
+ branch has them — uncommitted edits included — while a wait still counts as met
747
+ only on the base branch, so you can confirm it reproduces the plan you had
748
+ before landing it.
749
+
750
+ **The epic's first push retires the wave sub-issues.** An epic has no phases,
751
+ so every phase sub-issue its snapshot still remembers is a leftover of the plan
752
+ it was converted from: the push closes each as not planned and unlinks it from
753
+ the epic's issue, leaving the members as its only sub-issues. A tracker that
754
+ cannot retire one names it, to close by hand.
726
755
 
727
756
  ### Kind routing — any door, the right spec
728
757
 
@@ -880,6 +909,14 @@ status also lives in the tracker when a ticketing provider is linked. (There are
880
909
  no `00-index.md` summary files — the folder tree, headers, and State logs are
881
910
  queried directly.)
882
911
 
912
+ Under `land.specDocs: "branch"` a spec is not on the base branch until its
913
+ work lands, so `specs/backlog/` there misses it. `gating check` and
914
+ `epic status` therefore also read the spec folders each spec branch changed —
915
+ local branches, then remote-tracking ones as of the last fetch, never
916
+ fetching — and a branch copy wins over the base copy unless the base branch
917
+ has already finished that spec. A branch copy can make an epic member visible;
918
+ it never meets a wait, which is still read only off the base branch.
919
+
883
920
  ## Rules
884
921
 
885
922
  - If a spec already exists, update it — don't rewrite from scratch.
@@ -144,6 +144,13 @@ mentioning. The whole reason the stack exists is that the engine was being asked
144
144
  to guess where the reader was sitting, and it guessed wrong three separate ways
145
145
  in one day; a skill re-deciding that in prose is the same guess one layer up.
146
146
 
147
+ **And it holds outside a skill too.** Whenever you relay engine output that
148
+ carries a stack — `epic status` asked in passing, a `resolve`, an answer to a
149
+ question — pass on every tier, every `also:` line with its label, and the
150
+ `remote` line, never the one URL that looked like the answer. An agent asked
151
+ about an epic once replied with the member list and the loopback link alone,
152
+ and the reader on a phone was left with nothing they could open.
153
+
147
154
  **Three tiers, always all three, in this order.**
148
155
 
149
156
  | Tier | Is | Off when |
@@ -448,7 +455,7 @@ behind it — say nothing rather than reporting that there was nothing to report
448
455
  | `Built` | What the run produced — the code, the edits, the spec written. |
449
456
  | `Tests` | The result and the command that produced it. |
450
457
  | `Notes` | What this run hit and handled — one short paragraph. Named `Snags` once, which announced a problem before the reader had read one; most of what belongs here is neither good nor bad, just worth knowing. A wrong turn, a guard that fired, a check of yours that turned out to be a false negative. Not a caveat on the outcome (`⚠️` and `Why` carry those) and not future work (`Follow-ups` carries that): this is what happened on the way. |
451
- | `Landed` | A fast-forward, a tag, a cherry-pick — or in PR mode the PR itself: `PR #14 (draft) updated` · `PR #14 opened — finish after merge` · `PR #14 merged` · `held — not pushed` (a declined consent is a true outcome, not a failure). |
458
+ | `Landed` | A fast-forward, a tag, a cherry-pick — or in PR mode the PR itself: `PR #14 (draft) updated` · `PR #14 opened — finish after merge` · `PR #14 merged` · `held — not pushed` (a declined consent is a true outcome, not a failure) · `not pushed · <command> publishes it` (a push suggested rather than asked, as `/spec`'s branch lane does). |
452
459
  | `Worktree` | A worktree provisioned, entered, or torn down. |
453
460
  | `Untouched` | Uncommitted work the run deliberately left alone — whose, and how much. |
454
461
  | `Review` | The rendered diff page: files, `+`/`−`, and the stack — the same tiers the banner lists, labelled, run together with `·` because a row is one cell, with any `network` alternates inline after the network URL (`also <url> (tailnet)`), plus `live` where the engine reported one. **No question** — a row cannot be waited on, so a question in one is unanswerable by construction (see *asking implies waiting*). **Omitted entirely when the run is waiting on a verdict**: the banner after the block carries it instead, and a row saying the same thing beside it splits the reader's attention across two places. |
@@ -620,23 +620,40 @@ on the branch you are standing on — so a spec left on its own branch would be
620
620
  invisible to everyone, including the next `/spec` run. The commit goes on the
621
621
  branch and then the branch goes onto the base:
622
622
 
623
- **Unless the project set `land.specDocs: "branch"`** — the lane for a base
624
- branch nobody may push, where the spec document rides the feature branch and
625
- lands with the work's PR. There both verdicts commit on the branch and
626
- **skip the integrate below entirely**; `commit-start` carries into
627
- `/spec-start` over the same worktree exactly as ever, and plain `commit` keeps
628
- the branch AND the worktree, because they are now the only copy of the
629
- document. Say the trade out loud in the report's `Notes`: the backlog is found
630
- through the tracker listing (or `git branch`), not `ls specs/backlog/` on base
631
- — and a later `/spec-cancel` of a never-started branch-mode spec deletes the
632
- branch and worktree with the spec document dying with them, no PR ever having
633
- existed. Under the default `"trunk"` everything below applies unchanged.
623
+ **Unless `land.specDocs` is `"branch"`** — set so in `env.config.json`, or
624
+ left unset in a project with a ticketing provider configured (its config file
625
+ under `specs/.core/`), where it is the default because the tracker already is
626
+ the backlog. It is the lane where the spec document rides its feature branch
627
+ and lands with the work. There both verdicts commit on the branch and
628
+ **touch no base at all**; `commit-start` carries into `/spec-start` over the
629
+ same worktree exactly as ever, and plain `commit` keeps the branch AND the
630
+ worktree, because they are the document's working copy. What the lane does
631
+ instead of landing is **publish the branch**, because an unpushed spec branch
632
+ is on one machine and nowhere else — the ticket's summary cannot rebuild it.
633
+
634
+ **The same command answers both lanes; you do not choose between them:**
634
635
 
635
636
  ```
636
- skitterspec spec-env integrate <name>
637
+ skitterspec spec-env integrate <name> --docs
637
638
  ```
638
639
 
639
- It plans a rebase onto the base branch in the worktree, then a
640
+ Under `"trunk"` it prints the ordinary land, unchanged. Under `"branch"` it
641
+ says `spec docs ride the branch` and plans one push of the spec's branch,
642
+ consent-gated like every push in this workflow: already on the remote at HEAD
643
+ is honoured and runs nothing; otherwise it holds the push.
644
+ **Do not ask, and do not run it** — a suggestion is not a question.
645
+ Report `Landed` as `not pushed`, with the held command it printed beside it as
646
+ the way to publish, so it sits in the table for the reader to take or leave. A
647
+ question here interrupted the end of an authoring run for something that can
648
+ wait until the reader chooses to. Already on the remote reports
649
+ `pushed <remote>/<branch>`. A clone with no such remote prints that the branch
650
+ stays local; report that as the `Landed` row.
651
+
652
+ Say the trade in the report's `Notes`: the backlog is found through the
653
+ tracker listing (or the spec branches), not `ls specs/backlog/` on base. Under
654
+ `"trunk"` everything below applies unchanged.
655
+
656
+ Under `"trunk"` it plans a rebase onto the base branch in the worktree, then a
640
657
  `merge --ff-only` in the primary checkout — run the commands it prints. It
641
658
  refuses on a dirty tree, which is correct here: the commit ran first, so anything
642
659
  still uncommitted at this point is not this spec's and the land must not proceed.
@@ -279,6 +279,13 @@ only ordering that survives.
279
279
  a fault — and if the user wants the remote branch gone anyway, that is their
280
280
  call to make explicitly, not something to tidy away on their behalf.
281
281
 
282
+ **One unlanded branch does get the section: a never-started spec under `land.specDocs: "branch"`**, whose branch holds nothing but its own
283
+ documents. Its remote copy backs up only the spec being cancelled — the
284
+ ticket keeps the record — and left there it goes on reading as backlog to
285
+ every check that scans spec branches. Ask exactly as above. On a no, say in
286
+ the report that the branch stays on the remote and will still read as
287
+ backlog until someone deletes it.
288
+
282
289
  **In PR mode the same confirm-first section may carry the PR abandon**
283
290
  (`gh pr close` / `az repos pr update --status abandoned`): a cancelled spec
284
291
  must not leave a live PR behind — it is noise with a merge button on it.
@@ -297,11 +297,46 @@ Then build it, following the project rules in `.claude/rules/*.md` and `CLAUDE.m
297
297
  - Never hardcode dates in tests; never run destructive commands against a real
298
298
  database — use the project's test database only.
299
299
 
300
+ ### Manual steps — list them, then ask
301
+
302
+ Some tasks are a person's to do: every task in an **Issue** spec, and any task
303
+ you cannot perform yourself — operate a UI, check a device, confirm something
304
+ on a board, run a manual test pass. That is a **judgment**, not a marker: there
305
+ is no `(manual)` tag to look for, and a spec written before this rule has none.
306
+
307
+ Build the tasks before the first manual one as usual. Then **stop at it** and
308
+ print **every remaining manual step of this phase, verbatim and numbered**, as a
309
+ plain markdown list in the conversation — never fenced, and
310
+ **never only the phase file's path**. A pointer to the file sends the reader
311
+ out of the terminal to find out what to do, which is the failure this exists to
312
+ fix; the steps themselves are what they act on.
313
+
314
+ Then ask one question, with three answers:
315
+
316
+ - **All done** — tick those steps and carry on to the end of the phase.
317
+ - **Some failed** — the picker cannot list the steps (it holds four options and
318
+ a phase can hold more), so ask in prose which numbers failed and what
319
+ happened. Write a dated note under each failed task, leave it unticked, tick
320
+ the rest. Where what happened is a defect, offer **`/spec-bug`** — confirm,
321
+ never switch.
322
+ - **Not yet** — tick nothing.
323
+
324
+ This is the mid-run question `.claude/rules/spec-reports.md` already allows —
325
+ whether a person did something is a question you cannot answer yourself — so it
326
+ needs no new shape in the report.
327
+
328
+ **Some failed or Not yet leaves the phase `🔄`, and stops the run there.** Code
329
+ tasks after an unconfirmed step are not built past it, and the phase did not
330
+ end: **skip §4's done-marking and §5 entirely** — no page, no arm, no wait.
331
+ End `⚠️` and name `/spec-next` in `Next`; it re-lists the same unticked steps.
332
+
300
333
  ## 4. Record progress
301
334
 
302
335
  - In the **phase file**: tick completed tasks (`- [x]`), flip its heading to `✅`,
303
336
  and set its `> **Status:**` to `Done`.
304
337
  - In **`00-overview.md`**: flip the matching phase-index row to `✅`.
338
+ - A manual step answered **Some failed** keeps its box unticked with its note,
339
+ and the phase is not marked done (§3, *Manual steps*).
305
340
  - If anything changed from the plan (a decision, a deviation, a discovered
306
341
  constraint), add a dated **Changelog** entry in `00-overview.md`.
307
342
  - If new work surfaced, add it as tasks to the appropriate phase file (or add a
@@ -645,7 +680,9 @@ the shape; this section carries only what is specific here.
645
680
 
646
681
  - `✅` — the phase is built and its tests are green.
647
682
  - `⚠️` — built and green, with something worth knowing (a mirror that did not
648
- refresh, a deviation from the plan).
683
+ refresh, a deviation from the plan) — or stopped at manual steps answered
684
+ **Some failed** or **Not yet**: the phase stays `🔄`, `Notes` says which steps
685
+ are open, and `Next` is `/commit, then /spec-next` to pick them up.
649
686
  - `❌` — the phase's tests are red, or it stopped part-way. Quote the failure.
650
687
  - `⏸` — no spec in flight, or the name given does not match the one that is.
651
688
 
@@ -451,8 +451,31 @@ invoke it yourself.
451
451
 
452
452
  **An epic has no phase 1.** `spec-env up` gives it a documents-only tree (no
453
453
  `setup`, no Docker) whether or not `--docs` was passed, because its work is its
454
- members'. Skip this step and step 5, end with the block, and name
455
- `skitterspec epic status <name>` in `Next`.
454
+ members'. Skip this step and step 5, and end with the block — but first ask
455
+ what the epic needs started:
456
+
457
+ ```
458
+ skitterspec epic status <name> --json
459
+ ```
460
+
461
+ Its `rows` carry each member's next action, and its `page` the epic page's
462
+ tiers. Two things go in the block, both copied from it rather than composed:
463
+
464
+ - **`Next`** names the first members to start — one `/spec-start <member>`
465
+ for each row whose `next.verb` is `start`, **in a new tab each**, and only as
466
+ many as there are free lanes (`freeLanes`; all of them when it is null). A
467
+ start qualified `no free lane` or `clashes with …` is not offered here. None
468
+ ready is a true answer: say what the first wave waits on.
469
+ - **`Review`** carries the epic page's stack — `local`, `network`, `remote`,
470
+ as `page.tiers` gives them — or, where `page.off`, the command that starts
471
+ the server. It is a page to come back to, not one to answer: nothing waits
472
+ on it, so it is the row and never the banner.
473
+
474
+ **This tab is the epic's from here.** The members are built in tabs of their
475
+ own; this one is where the operator comes back to see what each needs. On a
476
+ phone the in-app browser has to close to switch tabs, so the page link must be
477
+ one command away rather than scrolled past: **`/epic`** re-shows the table and
478
+ the page, and the block names it.
456
479
 
457
480
  **`checkout` mode — carry straight on into `/spec-next`** in this session: it
458
481
  marks phase 1 started, refreshes the mirror again, builds it with tests and
@@ -518,11 +541,15 @@ the shape; this section carries only what is specific here.
518
541
  is **not** on this list in `worktree` mode — it is an `Untouched` row on a
519
542
  `✅`.
520
543
 
521
- **Fields:** `Tracker` · `Branch` · `Spec` · `Worktree` · `Untouched` · `Follow-ups` · `Next`
544
+ **Fields:** `Tracker` · `Branch` · `Spec` · `Worktree` · `Untouched` · `Review` · `Follow-ups` · `Next`
522
545
 
523
546
  `Worktree` carries the path, because the session is now standing in it and the
524
547
  operator's next command depends on knowing that. `Next` is `/spec-next`.
525
548
 
549
+ **An epic is the one exception, both ways.** `Review` appears only for an epic,
550
+ carrying its page's stack, and its `Next` is the members to start in new tabs
551
+ — with `/epic` to bring the table and the page back (step 6).
552
+
526
553
  `Untouched` appears only when `spec-env up` reported uncommitted work that was
527
554
  not this spec's — say how much and whose, and **keep the verdict `✅`**. Nothing
528
555
  went wrong: a worktree carries nothing, so that work was never in play.
@@ -27,6 +27,11 @@ const { run, HELP } = require('../src/cli.js')
27
27
  require('../src/env/config.js').setProviderEnvDefaults(
28
28
  require('../src/vendor/jira/config.js').ENV_CONFIG_DEFAULTS,
29
29
  )
30
+ // Its config file too: present, it is what makes `land.specDocs` default to
31
+ // "branch" (see common src/env/config.js, setProviderConfigFile).
32
+ require('../src/env/config.js').setProviderConfigFile(
33
+ require('../src/vendor/jira/config.js').CONFIG_FILE,
34
+ )
30
35
  const {
31
36
  PROVIDER_COMMANDS,
32
37
  providerHelpSection,
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@skitterbyte/skitterspec-jira",
3
- "version": "2.6.0",
3
+ "version": "2.8.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",