@lacodda/rigger 0.34.0 → 0.35.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.
- package/README.md +4 -5
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -11,18 +11,17 @@
|
|
|
11
11
|
|
|
12
12
|
## Why
|
|
13
13
|
|
|
14
|
-
Run more than a handful of projects and the record of them scatters: a plan in one file, a changelog in another, a session log the assistant writes for itself, a
|
|
14
|
+
Run more than a handful of projects and the record of them scatters: a plan in one file, a changelog in another, a session log the assistant writes for itself, a list of what is next kept by hand. You stop reading it, because prose cannot be filtered or summed up across projects. The assistant reads it every session at full price. And what actually shipped lives in git, where nobody looks.
|
|
15
15
|
|
|
16
|
-
rigger keeps the record as data, in one local SQLite file, and derives the rest from it: the packet an assistant starts from, the questions waiting for you, the
|
|
16
|
+
rigger keeps the record as data, in one local SQLite file, and derives the rest from it: the packet an assistant starts from, the questions waiting for you, the order projects come round in - with git, not the plan, deciding what shipped.
|
|
17
17
|
|
|
18
18
|
## A day with rigger
|
|
19
19
|
|
|
20
20
|
Plan a stage, and write down what was decided and what only you can answer:
|
|
21
21
|
|
|
22
22
|
```console
|
|
23
|
-
$ rigger version add sample v0.1.0 --title "First light" --task "read a sheet" --task "write the report"
|
|
23
|
+
$ rigger version add sample v0.1.0 --title "First light" --task "read a sheet" --task "write the report"
|
|
24
24
|
Added v0.1.0 to sample, with 2 tasks
|
|
25
|
-
aimed at 2026-W43 - the week of 2026-10-23
|
|
26
25
|
|
|
27
26
|
$ rigger note sample "Which file formats come first?" --kind question
|
|
28
27
|
Asked the owner about sample; it waits in the inbox until answered
|
|
@@ -118,7 +117,7 @@ The whole first week, command by command: [Your first week](https://lacodda.gith
|
|
|
118
117
|
- **Facts from git.** A tag means the version shipped, on that date; the plan cannot claim more than git confirms, and `doctor` names where they part.
|
|
119
118
|
- **An MCP server as the assistant's only pen**, and a context packet held to a token budget.
|
|
120
119
|
- **`rigger go`** - which project to work on now, the one reason it comes first, and your assistant started on it; nothing new starts while a tag is not out.
|
|
121
|
-
- **Your inbox
|
|
120
|
+
- **Your inbox and a queue with weights** - `rigger queue` puts every project in the order it gets a turn, `rigger priority` sets how often one comes round - derived from the same record rather than kept by hand.
|
|
122
121
|
- **`--json` on every command**, each field held by a test to its reference page.
|
|
123
122
|
- **Hubs as an export.** Markdown notes are written from the record and kept that way: the end of each sitting writes again what nobody touched, and `doctor --hubs` names what somebody did. A hand-kept hub [moves into the record](https://lacodda.github.io/rigger/guides/from-a-hub/) in one command, every note in it.
|
|
124
123
|
|
package/package.json
CHANGED
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@lacodda/rigger",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.35.0",
|
|
4
4
|
"rigger": {
|
|
5
|
-
"binary": "v0.
|
|
5
|
+
"binary": "v0.35.0"
|
|
6
6
|
},
|
|
7
7
|
"description": "One seat for all your projects and tasks: a local record of what is done, what is next and when it ships - read by you and your coding assistant",
|
|
8
8
|
"license": "MIT",
|