@harborppm/cli 0.53.0 → 0.55.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 +19 -2
- package/dist/app.mjs +25161 -23240
- package/lib/cli.mjs +286 -18
- package/lib/format.mjs +123 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -138,13 +138,19 @@ harbor open [TASK|PROJECT] open it on the website (or Today)
|
|
|
138
138
|
harbor invite EMAIL [--viewer] invite someone to your harbor by email
|
|
139
139
|
harbor calendar [--program P] [--new|--off] your private calendar link (.ics)
|
|
140
140
|
harbor roadmap PROJECT [--publish] [--off] a project's public roadmap: read, publish or take it down
|
|
141
|
+
harbor shore PROGRAM [--url URL] [--on forecast,health,notes] [--off KINDS] [--test] [--remove]
|
|
142
|
+
a program's Slack, Discord or Teams channel: the morning
|
|
143
|
+
forecast, health changes and notes for later post there
|
|
141
144
|
|
|
142
145
|
harbor program "NAME" [--portfolio P] [--lead me|NAME] [--starts DATE]
|
|
143
146
|
[--ends DATE]
|
|
144
147
|
harbor project "NAME" --program P [--lead me|NAME] [--starts DATE]
|
|
145
|
-
[--ends DATE] [--budget N]
|
|
148
|
+
[--ends DATE] [--budget N] [--from "DONE PROJECT"]
|
|
149
|
+
--from: dead reckoning, its tasks due when
|
|
150
|
+
they really finished in that project
|
|
146
151
|
harbor add "TITLE" --project P [--assignee me|NAME] [--due DATE]
|
|
147
|
-
[--priority low|medium|high|urgent] [--status S] [--
|
|
152
|
+
[--priority low|medium|high|urgent] [--status S] [--comment TEXT]
|
|
153
|
+
[--over-limit] no TITLE: one title a line from stdin
|
|
148
154
|
harbor start TASK | submit TASK | done TASK [--confirm] [--over-limit]
|
|
149
155
|
harbor edit TASK [--title T] [--assignee me|none|NAME] [--due DATE|none]
|
|
150
156
|
[--priority P] [--status S] [--notes TEXT]
|
|
@@ -184,6 +190,8 @@ harbor note PROJECT ["NOTE"] [--opens DATE|--milestone NAME|--off-track]
|
|
|
184
190
|
harbor sound TASK [DAYS] [--why TEXT] [--ask NAMES|crew] [--settle DAYS]
|
|
185
191
|
harbor soundings [PROJECT]
|
|
186
192
|
harbor limit PROJECT [COLUMN N|none]
|
|
193
|
+
harbor week [--next|--last|--week DATE] [--review]
|
|
194
|
+
harbor week TASK DAY [--hours N] | week TASK --off [DAY] | week --day-hours N
|
|
187
195
|
harbor init [PROJECT] [--hook] [--dry-run] a project's tasks as files in this repository
|
|
188
196
|
harbor init --local [NAME] a plan in this folder alone, no account
|
|
189
197
|
harbor sync [--quiet] [--dry-run] the files and the website, in step both ways
|
|
@@ -191,6 +199,9 @@ harbor handover PERSON [--to NAME] [--until DATE] [--note TEXT] [--keep ID,ID] [
|
|
|
191
199
|
harbor handback PERSON
|
|
192
200
|
harbor fog [--project P] [--list] tasks nobody has touched for three weeks, one at a time
|
|
193
201
|
harbor fog keep TASK it's still needed: out of the fog
|
|
202
|
+
harbor lifeboats [--program P] work only one person knows, each with a second pair of hands
|
|
203
|
+
harbor lifeboats N [--person NAME] adds that second pair of hands
|
|
204
|
+
harbor follow TASK|"RISK" --person NAME someone follows it too
|
|
194
205
|
harbor agent [--agent NAME]
|
|
195
206
|
harbor agent report TASK "WHAT YOU DID" [--start] [--agent NAME]
|
|
196
207
|
```
|
|
@@ -199,8 +210,14 @@ harbor agent report TASK "WHAT YOU DID" [--start] [--agent NAME]
|
|
|
199
210
|
|
|
200
211
|
`harbor fog` walks through the open tasks nobody has opened, moved, edited or commented on for three weeks, one at a time: `k` still needed (clears the fog), `d` a new date, `x` drop it, `s` skip, `q` stop. Piped or with `--list` it just lists them. On the board, in the app and on the website, those cards show dimmed.
|
|
201
212
|
|
|
213
|
+
`harbor lifeboats` lists the work only one person has touched (a project, their corner of one, a task others wait on, their serious risks), numbered, each with someone who has room this week and already works nearby. `harbor lifeboats 2` puts that person on line 2 as a second pair of hands (`--person NAME` for someone else); `harbor follow RR-4 --person Sam` does it for one task. Following doesn't take the work over. `harbor raid "DECISION" --still-stands "WHY"` says a decision that came back for a look still stands.
|
|
214
|
+
|
|
202
215
|
Agents on the crew: put an AI app on People with Add an agent and assign it tasks like anyone else. An agent working through the CLI (Claude Code, say) runs `harbor agent` for its tasks, in progress first, with their notes, checklists and latest comments. When it's done, `harbor agent report RR-4 "Drafted 12 questions; two need Dana"` adds its note as the agent's comment and moves the task to In review for a person to check. An agent never marks its own work Done.
|
|
203
216
|
|
|
217
|
+
`harbor week` is your own week, and only you see it: Monday to Friday with the tasks you put on each day, the hours each should take against the hours you work (`--day-hours 8`; 7 unless you say), a warning on a day that's too full, and your open tasks not on a day yet. `harbor week RR-42 wed --hours 3` puts a task on Wednesday (`--next` for next week), `harbor week RR-42 --off` takes it off the week, and from Friday (or with `--review`) it says what you planned against what you finished. The website's Your week is the same plan, with drag and drop.
|
|
218
|
+
|
|
219
|
+
`harbor add --project Trail --comment "From Monday's call" < list.txt` adds one task per line of the file, each with the comment.
|
|
220
|
+
|
|
204
221
|
`harbor limit RR` prints how many tasks each of a board's columns takes at once; `harbor limit RR doing 8` changes one (1 to 20, or `none` for no limit), if you own the harbor. `harbor projects --json` carries each board's `limits` too.
|
|
205
222
|
|
|
206
223
|
`harbor premortem` runs a pre-mortem with your crew: `--start` asks everyone "it's after the end date and this project failed: what happened?", each person adds answers alone for five minutes, and then the answers show together on the project's Risks & issues tab, where each becomes a risk in one click. On its own it prints the question and the answers you can see. Once a project is Done, `harbor voyage` prints its voyage log (planned against actual dates, the biggest slips, the risks that came true, who closed the most, and the crew's lines) and adds yours. `harbor note` leaves a note for later on a project: it stays sealed (the crew sees only that it's there and who left it) until its day, until one of the program's milestones is reached, or until the project turns Off track, and then it opens at the top of the project and in the brief. `harbor sound TASK --ask crew` takes a sounding: it asks you, the task's owner and whoever has open work on its project how many working days the task will take (`--ask "Sam,Priya"` picks who). Each person answers alone with `harbor sound TASK 4 --why "…"`, and nobody sees the others' numbers until everyone has; then `harbor sound TASK` shows the spread, an estimate when the guesses are close, or "talk about this first" when they're far apart, and `--settle DAYS` records what you agreed. `harbor soundings` lists them, the ones waiting on your answer first.
|