@skitterbyte/skitterspec-jira 2.8.0 → 2.9.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.
@@ -17,6 +17,12 @@ phone. The diff never passes through the model, so the page costs no context
17
17
  tokens however large it is; the optional written review is the part that costs,
18
18
  and it is offered rather than assumed. `/spec-next` writes the page at the end of
19
19
  every phase. **`skitterspec status`** lists what is in flight across worktrees.
20
+ At the end of the day, **`/spec-tada`** is the ta-da list: what you did across
21
+ every project, grouped by spec — what landed, what was explored, what is still
22
+ in flight — ending in a three-line standup (`skitterspec tada` is the engine).
23
+ It covers the projects that share this one's `project.category`;
24
+ **`skitterspec project`** shows and sets the name and category, and
25
+ `/spec-init` asks for both.
20
26
 
21
27
  **Handing the review back.** The page takes marks: tick `✓ accept` per file as
22
28
  you read, note anything against a line or a whole file, answer the questions a
@@ -1,5 +1,9 @@
1
1
  {
2
2
  "mode": "worktree",
3
+ "project": {
4
+ "name": "",
5
+ "category": ""
6
+ },
3
7
  "worktree": {
4
8
  "root": "../{repo}-wt",
5
9
  "folderPattern": "{slug}"
@@ -65,6 +65,18 @@ through to a documented conservative default; see the field notes below.
65
65
  // Not to be confused with `seedFiles.mode`, which is "symlink" | "copy".
66
66
  "mode": "worktree",
67
67
 
68
+ // What this project is called and which group it belongs to.
69
+ "project": {
70
+ "name": "", // heads every generated page — reviews, the
71
+ // served index, the epic page, the ta-da page.
72
+ // Empty: the primary checkout's folder name. Read
73
+ // before the superseded `review.projectName`.
74
+ "category": "" // a free label — "work", "personal", a client.
75
+ // `skitterspec tada` run here reports only the
76
+ // projects with the same category (compared
77
+ // case-insensitively); empty here reports all.
78
+ },
79
+
68
80
  "worktree": {
69
81
  "root": "../{repo}-wt", // dir that holds all spec worktrees; sibling of
70
82
  // the primary checkout, never nested inside it.
@@ -568,11 +580,9 @@ through to a documented conservative default; see the field notes below.
568
580
  // because a commit made under rules nobody configured must not read as one
569
581
  // made under /commit.
570
582
  //
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: "".
583
+ // `projectName` is SUPERSEDED by `project.name` and still read beneath it,
584
+ // so a config that set it keeps its name. Set `project.name` instead.
585
+ // Default: "".
576
586
  //
577
587
  // THERE IS NO OFF SWITCH. `"none"` existed and was removed: it produced a
578
588
  // verdict that records itself and does nothing, which is the one thing a
@@ -16,9 +16,11 @@ and lifecycle stay consistent. Each sets a status on the spec header
16
16
  | `/spec-start` | Put a spec in flight — provision its branch, then build phase 1 | `In Progress` | `specs/in-progress/` |
17
17
  | `/spec-next` | Build the next phase of the spec this session is in (re-run per phase) | `In Progress` (unchanged) | (unchanged) |
18
18
  | `/spec-reviewed` | Pick up a review approved on the page — offered by its code, claimed on your word | (unchanged) | (unchanged) |
19
+ | `/spec-epic-next` | Name the epic member that can start now, as the `/spec-start` to type in a new tab — a picker when several can; reads only | (unchanged) | (unchanged) |
19
20
  | `/spec-to-main` | Land the branch on the base (rebase + ff) **without** finishing — for running the work in CI / a shared env mid-spec; repeatable | `In Progress` (unchanged) | (unchanged) |
20
21
  | `/spec-complete` | Verify all phases done + tests green; land + tear down | `Complete` | `specs/complete/` |
21
22
  | `/spec-cancel` | Record progress, stamp a reason on the header; tear down | `Cancelled` | `specs/cancelled/` |
23
+ | `/spec-tada` | A ta-da list — recap what you did in Claude Code over a window, across every project, by project then spec, ending in a standup. Read-only | (unchanged) | (unchanged) |
22
24
  | `/spec-init` | Bootstrap/repair this workflow in a project (idempotent) | — | — |
23
25
 
24
26
  **Skills vs commands.** The table above lists **skills** — Claude reads them and
@@ -71,6 +73,28 @@ branch. Beneath it, `skitterspec spec-env nospec <name>` records the branch —
71
73
  and that record is what makes a name with nothing under `specs/**` resolvable by
72
74
  `review`, `integrate`, `down` and a bare `resolve`.
73
75
 
76
+ **`/spec-tada` reads, and moves nothing.** It is in the table because it
77
+ reports in the unit the table is about — a spec — but it changes no status,
78
+ writes no file and commits nothing. `skitterspec tada` reads Claude Code's own
79
+ transcripts down to the prompts a person typed and folds each session into
80
+ the **repo** it worked in, so a session that moved into `../<repo>-wt/<slug>`
81
+ is that repo's work, not a project of its own. A commit already on the base
82
+ branch is attributed by the spec folder it touched or its `Refs:` ticket, never
83
+ by a branch that happens to contain it — a spec branch cut this afternoon
84
+ contains all of this morning. It is model-invocable, because "what did I do
85
+ today?" should reach it.
86
+
87
+ **A report covers one category.** `project.category` in `env.config.json`
88
+ decides which projects share a report — only those with the category of the
89
+ repo it runs from, and an uncategorised project is in nobody's but its own
90
+ (`--all-projects` takes everything). `project.name` is what heads the page,
91
+ and every review page, with the repo folder as the fallback.
92
+ `skitterspec project` shows both and sets them (`--name`, `--category`) by
93
+ editing only those values; `--categories` lists what your other projects
94
+ already use, so one category is not spelled two ways. `/spec-init` asks for
95
+ both — on an existing config through a `/no-spec` branch, since the base
96
+ branch is a landing zone.
97
+
74
98
  **`/allow-main` is the fourth command.** It is user-only for a different reason
75
99
  from the other three: `/spec-connect`, `/spec-live` and `/spec-remote-review`
76
100
  are marked that way because there is no judgment to apply. This one is marked that
@@ -124,7 +148,7 @@ skip — never a flag. Putting the flag on `/commit` was the other suggestion an
124
148
  is worse: `/commit` belongs to skittership, which is why the gate is enforced
125
149
  by a hook rather than by editing that skill.
126
150
 
127
- **`/epic` is the sixth command**, and it is user-only for the mild reason: it
151
+ **`/spec-epic` is the sixth command**, and it is user-only for the mild reason: it
128
152
  pre-executes `skitterspec epic status` and relays it, so there is no judgement
129
153
  to apply. It exists for the tab an epic is run from — each member is built in
130
154
  a tab of its own, and on a phone the in-app browser has to close to switch
@@ -257,7 +257,7 @@ same files. Propose it as *"several specs with an order between them → epic"*,
257
257
  and on a yes write the epic **and** each member as its own spec — the epic is
258
258
  not a container for their phases (see **Writing an epic** below).
259
259
 
260
- There is no `/spec-chore`, `/spec-issue` or `/spec-epic` and none should be added: one entry
260
+ There is no `/spec-chore`, `/spec-issue` or epic-writing door and none should be added (`/spec-epic` reads an epic's status; it writes nothing): one entry
261
261
  point, one grill, and the kind is an output of understanding the work rather
262
262
  than a door the user must pick before describing it. The kinds with their own
263
263
  doors — bug, hotfix, and the **incident**, an outage or degradation of a live
@@ -265,6 +265,12 @@ least: the reader has just finished something and cannot tell whether a line
265
265
  about another spec followed from it. `Next` is one action for this spec, and
266
266
  `/spec-list` is where the wider picture lives if they want it.
267
267
 
268
+ **An epic member is the one exception to that `Next`.** When the spec carries
269
+ `> **Epic:**`, its own work is done and the next thing for that work is its
270
+ epic's: `Next` is **`/spec-epic-next`**, which names the member that can start
271
+ now. Name the command and nothing else — which members are ready is that
272
+ skill's to read, and listing them here is the survey this section forbids.
273
+
268
274
  `Landed` says how, because the two ways differ: a fast-forward names the base
269
275
  and the commit, a hotfix names the release tag, whether it was pushed, and the
270
276
  `main` carry — and a release tag that has not been pushed is a `⚠️`, not a `✅`. `Worktree` says
@@ -0,0 +1,83 @@
1
+ ---
2
+ name: spec-epic-next
3
+ description: Find the member of an epic that can start now and name the `/spec-start` to run for it in a new tab — asking which when several can, and saying why when none can. Reads only; it starts, provisions and moves nothing. Bare, it uses the epic or member worktree you are standing in. Use when the user says "/spec-epic-next", "start the next spec in the epic", "what's next in this epic", or has just completed an epic member.
4
+ ---
5
+
6
+ # /spec-epic-next — which epic member to start next
7
+
8
+ > Stay silent while this runs — speak only to ask something you cannot answer
9
+ > yourself, or to report a failure at the moment it happens. Read
10
+ > `.claude/rules/spec-reports.md` before reporting; it defines the block this
11
+ > skill ends with.
12
+
13
+ An epic's members are built in tabs of their own, and the tab this runs in
14
+ stays whatever it was — the epic's coordinator, or a member that just finished.
15
+ So this skill **picks and prints**: its answer is `/spec-start <member>` to
16
+ type **in a new tab**. It writes nothing, provisions nothing, and moves no
17
+ session. Starting the member is `/spec-start`'s job, in that tab.
18
+
19
+ ## 1. Ask the engine
20
+
21
+ ```
22
+ skitterspec epic status [<epic>] --json
23
+ ```
24
+
25
+ Pass the epic when the invocation names one. Bare, the engine resolves it from
26
+ the worktree you are standing in — the epic's own, or a member's (its
27
+ `> **Epic:**` header). When it resolves nothing (`epic: null`), stop with `⏸`
28
+ and name `/spec-epic-next <epic>` in `Next`, with the epics its `inFlight`
29
+ lists as the candidates. **Never pick an epic from conversation**: a
30
+ spec discussed is not the epic in hand, and the engine already knows where you
31
+ are standing.
32
+
33
+ Read its `steps`, `groups` and `freeLanes`. A step whose `where` is `new-tab`
34
+ is a member that may start now, in a free lane; its `command` is the
35
+ `/spec-start` to type and its `caution` any clash. Do not re-derive that from
36
+ `rows` or the headers. The engine decides what can start and caps it at the
37
+ free lanes, and it is the same answer the epic page and `/spec-epic` print.
38
+ Any second answer could disagree with them.
39
+
40
+ ## 2. Route on what it said
41
+
42
+ **Every member done.** The only step has `where: epic`, and its `command` is
43
+ `/spec-complete <epic>`. Say so, `✅`.
44
+
45
+ **No free lane.** `freeLanes` is `0` and `groups.ready` is not empty. Stop with
46
+ `⏸`: the lanes are the cap the epic chose, and this skill does not offer a way
47
+ past it. Name the members in `groups.inFlight`, which are what is holding the
48
+ lanes. The in-tab steps say what each needs to finish.
49
+
50
+ **Nothing ready.** `groups.ready` is empty. Stop with `⏸` and name what each
51
+ member in `groups.waiting` waits on (its row's `next.why`). A member the engine
52
+ could not read is in `waiting` with its reason, never in `ready`
53
+ (`.claude/rules/negative-checks.md`), so quote that reason rather than
54
+ treating the wait as met.
55
+
56
+ **One start step.** Name it. `Next` is its `command`, in a new tab, with its
57
+ `caution` beside it.
58
+
59
+ **Several start steps.** Offer a picker — one option per start step, plus
60
+ Cancel — and **never choose for them**. A member with a `caution` is listed
61
+ **with** its clash, not filtered out: `Area:` is what a spec says it will
62
+ touch, and `/spec-start` §4c raises the clash again when it starts. The engine
63
+ already puts the start with no clash first, so keep its order. A choice ends
64
+ `✅` with that member in `Next`; Cancel ends `⏸`.
65
+
66
+ ## Report
67
+
68
+ End with the block defined in `.claude/rules/spec-reports.md`. That file carries
69
+ the shape; this section carries only what is specific here.
70
+
71
+ **Verdicts**
72
+
73
+ - `✅` — a member was named or picked, or every member is done and the epic
74
+ itself is next.
75
+ - `⏸` — no free lane, nothing ready, a wait it cannot read, no epic resolved,
76
+ or the picker cancelled. Nothing changed — and nothing ever does here.
77
+
78
+ **Fields:** `Spec` · `Follow-ups` · `Next`
79
+
80
+ `Spec` names the epic and how far along it is, from the engine's
81
+ `progress` (`N of M done · K in flight`). `Next` is `/spec-start <member>` **in a new tab**, or on a `⏸` the
82
+ thing that would unblock it. Where several are startable the picker is the
83
+ control after the block, and `Next` names it.
@@ -27,14 +27,16 @@ clobber customised content. Finish with a summary of created vs already-present.
27
27
  > **Leave alone**. Non-interactively it only adds what's missing; `--resync` /
28
28
  > `--reset` (reset needs `--yes`) drive the stronger actions.
29
29
 
30
- The system is **fourteen skills**: `spec` (feature, chore or issue), `spec-bug` (bug),
30
+ The system is **sixteen skills**: `spec` (feature, chore or issue), `spec-bug` (bug),
31
31
  `spec-hotfix` (a bug fixed on a released tag),
32
32
  `spec-incident` (a live outage, recorded as it happens),
33
33
  `no-spec` (work that genuinely has none — off the base branch all the same),
34
34
  `spec-review`, `spec-start`,
35
35
  `spec-next`, `spec-diff` (read a spec's diff as a page),
36
- `spec-reviewed` (pick up a review you approved on that page), `spec-to-main`,
37
- `spec-complete`, `spec-cancel`, and this `spec-init`. The lifecycle is `backlog → in-progress → complete / cancelled`,
36
+ `spec-reviewed` (pick up a review you approved on that page),
37
+ `spec-epic-next` (name the epic member that can start now), `spec-to-main`,
38
+ `spec-complete`, `spec-cancel`, `spec-tada` (a ta-da list of what got done),
39
+ and this `spec-init`. The lifecycle is `backlog → in-progress → complete / cancelled`,
38
40
  with `.core` holding always-apply project rules.
39
41
 
40
42
  ## 0. Workspace mode (only when adopting isolation)
@@ -59,6 +61,36 @@ path, and records the answer on each spec. Leave it off and nothing appears:
59
61
  no question, no header, no check. Off is a perfectly good answer for a project
60
62
  that does not use flags.
61
63
 
64
+ ## 0c. Project name and category (only with isolation)
65
+
66
+ Two values in `env.config.json` that the rest of the tooling reads:
67
+ `project.name` heads every generated page (reviews, `/spec-tada`), and
68
+ `project.category` decides which projects share a `/spec-tada` report — a
69
+ project with no category is left out of everyone else's. Ask both, together:
70
+
71
+ - **Name** — default the repo folder's name, which is also what is used when it
72
+ is left empty. Accept it unless the operator wants another.
73
+ - **Category** — run `skitterspec project --categories` and offer what it
74
+ lists, most-used first, so `work` is not typed as `Work stuff` in the next
75
+ repo and splits a report in two. Then offer to **type a new one**, and to
76
+ **leave it empty** (this project stays out of every categorised report).
77
+
78
+ Where the answer goes depends on whether the file exists yet:
79
+
80
+ - **A fresh adoption** — pass them to the command that creates the file:
81
+ `skitterspec init --isolation --name "<name>" --category <category>`.
82
+ - **`env.config.json` already exists** — the change is work, and the base
83
+ branch is a landing zone, so make it on a `/no-spec` branch
84
+ (`project-settings`): run `skitterspec project --name "<name>" --category
85
+ <category>` in that worktree, which edits only those two values, then land
86
+ it on the verdict as `/no-spec` does. Never write it in the primary checkout
87
+ on the base branch.
88
+
89
+ `skitterspec project` with no flags shows what is set now and where each value
90
+ comes from — read it first on a re-run, and skip the question when both are
91
+ already what the operator wants. Without isolation there is no
92
+ `env.config.json` and the command refuses to create one, so skip this step.
93
+
62
94
  ## 1. Folders
63
95
 
64
96
  Create any that are missing; drop a `.gitkeep` into ones that would otherwise be
@@ -474,7 +474,7 @@ tiers. Two things go in the block, both copied from it rather than composed:
474
474
  **This tab is the epic's from here.** The members are built in tabs of their
475
475
  own; this one is where the operator comes back to see what each needs. On a
476
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
477
+ one command away rather than scrolled past: **`/spec-epic`** re-shows the table and
478
478
  the page, and the block names it.
479
479
 
480
480
  **`checkout` mode — carry straight on into `/spec-next`** in this session: it
@@ -548,7 +548,7 @@ operator's next command depends on knowing that. `Next` is `/spec-next`.
548
548
 
549
549
  **An epic is the one exception, both ways.** `Review` appears only for an epic,
550
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).
551
+ — with `/spec-epic` to bring the table and the page back (step 6).
552
552
 
553
553
  `Untouched` appears only when `spec-env up` reported uncommitted work that was
554
554
  not this spec's — say how much and whose, and **keep the verdict `✅`**. Nothing
@@ -0,0 +1,153 @@
1
+ ---
2
+ name: spec-tada
3
+ description: A ta-da list rather than a to-do list — recap what you did in Claude Code over a day (or since a date), across every project on this machine, grouped by project and then by spec — what landed, what was explored but not committed, what is still in flight — ending in a three-line standup. Use when the user says "/spec-tada", "what did I do today", "daily recap", "standup summary", "what have I done since Friday", or asks for an end-of-day summary.
4
+ ---
5
+
6
+ # /spec-tada — a ta-da list of what got done
7
+
8
+ > Stay silent while this runs — speak only to ask something you cannot answer
9
+ > yourself, or to report a failure at the moment it happens. Read
10
+ > `.claude/rules/spec-reports.md` before reporting; it defines the block this
11
+ > skill ends with.
12
+
13
+ Read-only. It writes nothing, commits nothing and publishes nothing — it reads
14
+ what already happened and says it back in the shape a standup wants.
15
+
16
+ ## 1. Get the digest
17
+
18
+ ```
19
+ skitterspec tada [--since <when> | --on <when>] [--here | --all-projects] [--chat]
20
+ ```
21
+
22
+ Map the request onto the flags and nothing else:
23
+
24
+ - **`--since <when>`** — from that day to now: "since Friday", "this week",
25
+ "the last three days".
26
+ - **`--on <when>`** — that one day: "what did I do last Friday", "on the 6th".
27
+ Neither flag is today.
28
+ - **`--here`** — "this repo", "this project": narrow to the repo the session is
29
+ standing in.
30
+ - **`--all-projects`** — "everything", "work and personal": every project on
31
+ the machine.
32
+ - **`--chat`** — "everything I talked about", "include the chats": keep the
33
+ prompts on branches with no spec too.
34
+
35
+ **The report is scoped by category without being asked.** Run from a project
36
+ whose `project.category` is set (in `specs/.core/env.config.json`), it covers
37
+ only the projects with the same category; uncategorised ones are left out. The
38
+ first line of the digest names the category when there is one — say it in
39
+ `Built`, so the reader knows what the report covers. Each project is shown by
40
+ its `project.name`.
41
+
42
+ A `<when>` is any of these, passed as the words the person used — no quoting:
43
+
44
+ | Kind | Examples |
45
+ |------|----------|
46
+ | named | `today` · `yesterday` · `friday` · `last friday` · `last week` |
47
+ | relative | `3 days ago` · `3d` · `2 weeks ago` · `2w` |
48
+ | a date | `2026-11-06` · `6 Nov` · `Nov 6` · `6 November 2026` |
49
+
50
+ A weekday is the most recent past one, so never more than a week back. A date
51
+ with no year is the most recent such date. `11/12` is refused rather than
52
+ guessed — it is a different day in London and New York — so translate a
53
+ numeric date only when the person's meaning is unambiguous, and write it as
54
+ `YYYY-MM-DD`.
55
+
56
+ **Read the text form, never `--json`.** It carries the same facts at a fifth of
57
+ the size, and the size is the whole cost of this skill.
58
+
59
+ **Never read a transcript yourself.** The engine reads them down to the prompts
60
+ a person typed — capped, and only the first and last few per session — and folds
61
+ each session into its repo, so a worktree is never mistaken for a project. A
62
+ transcript opened by hand is the thing the digest exists to avoid paying for.
63
+
64
+ A window the engine cannot read is refused with exit 1 and a line naming the
65
+ fix — relay it and stop with `⏸`. Everything else exits 0, a quiet day included.
66
+
67
+ **The digest quotes the person's own prompts.** It stays in this conversation:
68
+ do not paste it anywhere else, and never publish it.
69
+
70
+ ## 2. Write the recap
71
+
72
+ One section per project, then one entry per group. A group headed by a spec
73
+ (`feat-orders [#12]`) is that spec's work wherever it happened — its branch, its
74
+ worktree, or a commit on the base naming it. A group headed `<branch> — no spec`
75
+ is work that names none, and carries only its commits: prompts typed where no
76
+ spec was in play are left out, unless the session went on to a spec — then
77
+ they sit under that spec, as the conversation that led to it.
78
+
79
+ For each group, say what applies and skip what does not:
80
+
81
+ - **Done** — the lifecycle moves (`* written`, `* started`, `* phase N done`,
82
+ `* completed`) and the commits (`+ <sha> <subject>`). Say what changed in a
83
+ line, from the subjects — do not list every sha.
84
+ - **Explored** — a spec's sessions beyond what its commits say: what was
85
+ looked into, asked or decided, read off the prompts. The prompts are partial by
86
+ construction (`… N more` marks the cut), so say what they show, not that it
87
+ is everything.
88
+ - **In flight** — the `in flight:` line: where the spec stands and its next
89
+ action, as the engine wrote it.
90
+
91
+ Name a spec by its folder and its ticket exactly as the digest gives them. Keep
92
+ each entry to a line or two; a project with only in-flight rows gets one line
93
+ listing them.
94
+
95
+ Then the **standup** — three lines, no more:
96
+
97
+ - **Done:** the work that landed or moved, across every project.
98
+ - **Next:** the in-flight next actions that matter most.
99
+ - **Blockers:** a verdict waiting, a gate armed, a wait unmet — or `none`.
100
+ Only what the digest shows; never invent one.
101
+
102
+ ## 3. The page — only when asked
103
+
104
+ When the person asks for the recap as a page — "as a page", "something I can
105
+ read on my phone", "`--page`" — write the recap and standup you just wrote, as
106
+ markdown, to a temporary file, and run the same window again with it:
107
+
108
+ ```
109
+ skitterspec tada <the same flags> --page --summary <that file>
110
+ ```
111
+
112
+ **Where the project has a review server**, it saves the recap beside the
113
+ review notes and prints the page's stack — `local`, `network`, `remote` —
114
+ exactly as a review render does. The page is drawn per request, from the
115
+ day's facts as they stand when it is opened, with the recap on top and when
116
+ it was written. Relay every tier as the engine printed it, in the `Built`
117
+ row (`.claude/rules/spec-reports.md` carries the shape). Nothing waits on it:
118
+ it asks no verdict, so it is a row and never a banner.
119
+
120
+ **Where there is none** — no isolation, `review.serve: "never"` — it prints
121
+ one line, `page: file://…`, a file in the system temp folder that opens on
122
+ this machine only. Say so in `Notes`.
123
+
124
+ **Never publish it.** It quotes the person's prompts; sharing it is theirs to
125
+ do.
126
+
127
+ Not asked, it is not rendered — say once, at the end of `Notes`, that
128
+ `--page` would.
129
+
130
+ ## Report
131
+
132
+ The recap and standup are the body of the message; the block follows them and
133
+ is the last thing in it. That file carries the shape; this section carries only
134
+ what is specific here.
135
+
136
+ **Verdicts**
137
+
138
+ - `✅` — the recap is written. A window with nothing in it is still `✅`, said
139
+ as such: a quiet day is an answer.
140
+ - `⚠️` — written, but the digest said `cannot tell` somewhere. Name it in
141
+ `Notes`.
142
+ - `⏸` — the engine refused the window. Nothing was read.
143
+
144
+ **Fields:** `Built` · `Notes` · `Follow-ups` · `Next`
145
+
146
+ `Built` is the window and the counts — projects, specs, commits — and the
147
+ page's tiers (or its `file://` path) when one was rendered. `Notes` carries the digest's own closing
148
+ lines (`cannot tell`, torn-down worktrees counted elsewhere) and, when no page
149
+ was asked for, that `--page` renders one. `Next` is the one
150
+ in-flight action the standup put first, or `nothing in flight`.
151
+
152
+ **`Follow-ups` is always `none` here.** This skill reports work; anything it
153
+ notices belongs to the spec it is about.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@skitterbyte/skitterspec-jira",
3
- "version": "2.8.0",
3
+ "version": "2.9.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",