@skitterbyte/skitterspec-linear 19.7.0 → 19.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.
Files changed (46) hide show
  1. package/README.md +3 -1
  2. package/assets/claude-md-section.md +6 -0
  3. package/assets/core/env.config.json.example +5 -0
  4. package/assets/core/env.config.md +26 -5
  5. package/assets/review/page.html +9 -0
  6. package/assets/rules/spec-planning.md +65 -12
  7. package/assets/rules/spec-reports.md +8 -1
  8. package/assets/skills/spec/SKILL.md +31 -14
  9. package/assets/skills/spec-cancel/SKILL.md +7 -0
  10. package/assets/skills/spec-complete/SKILL.md +6 -0
  11. package/assets/skills/spec-epic-next/SKILL.md +83 -0
  12. package/assets/skills/spec-init/SKILL.md +35 -3
  13. package/assets/skills/spec-next/SKILL.md +38 -1
  14. package/assets/skills/spec-start/SKILL.md +2 -2
  15. package/assets/skills/spec-tada/SKILL.md +153 -0
  16. package/bin/skitterspec-linear.js +5 -0
  17. package/package.json +1 -1
  18. package/src/cli.js +473 -25
  19. package/src/env/config.js +57 -6
  20. package/src/env/epic.js +69 -19
  21. package/src/env/epicpage.js +87 -39
  22. package/src/env/epicread.js +41 -3
  23. package/src/env/integrate.js +48 -1
  24. package/src/env/nextaction.js +78 -1
  25. package/src/env/project.js +54 -3
  26. package/src/env/projectedit.js +148 -0
  27. package/src/env/resolve.js +1 -0
  28. package/src/env/review.js +21 -3
  29. package/src/env/serve.js +44 -8
  30. package/src/env/specbranches.js +120 -0
  31. package/src/env/teardown.js +18 -3
  32. package/src/gating.js +16 -4
  33. package/src/init.js +11 -3
  34. package/src/tada/commits.js +145 -0
  35. package/src/tada/digest.js +260 -0
  36. package/src/tada/format.js +37 -0
  37. package/src/tada/page.js +213 -0
  38. package/src/tada/repo.js +102 -0
  39. package/src/tada/serve.js +127 -0
  40. package/src/tada/specs.js +146 -0
  41. package/src/tada/transcripts.js +258 -0
  42. package/src/tada/window.js +156 -0
  43. package/src/vendor/provider-kit/src/apply.js +25 -1
  44. package/src/vendor/sync-core/src/compare.js +10 -2
  45. package/src/vendor/sync-core/src/push.js +14 -3
  46. /package/assets/commands/{epic.md → spec-epic.md} +0 -0
@@ -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.
@@ -40,6 +40,11 @@ const { run, HELP } = require('../src/cli.js')
40
40
  require('../src/env/config.js').setProviderEnvDefaults(
41
41
  require('../src/vendor/linear/config.js').ENV_CONFIG_DEFAULTS,
42
42
  )
43
+ // Its config file too: present, it is what makes `land.specDocs` default to
44
+ // "branch" (see common src/env/config.js, setProviderConfigFile).
45
+ require('../src/env/config.js').setProviderConfigFile(
46
+ require('../src/vendor/linear/config.js').CONFIG_FILE,
47
+ )
43
48
  const {
44
49
  PROVIDER_COMMANDS,
45
50
  providerHelpSection,
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@skitterbyte/skitterspec-linear",
3
- "version": "19.7.0",
3
+ "version": "19.9.0",
4
4
  "description": "Spec-driven development for Claude Code, with one-way Linear sync — a superset of @skitterbyte/skitterspec: the base filesystem workflow plus /spec-status · /spec-push and the spec-sync CLI. The repo is canonical; Linear is a generated mirror. Install this OR the base, not both.",
5
5
  "keywords": [
6
6
  "claude",