@harborppm/cli 0.47.0 → 0.49.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 CHANGED
@@ -174,23 +174,29 @@ harbor import FILE [--project P] [--portfolio P] [--no-people]
174
174
  harbor premortem PROJECT ["WHAT WENT WRONG"] [--start]
175
175
  harbor voyage PROJECT ["YOUR LINE"]
176
176
  harbor note PROJECT ["NOTE"] [--opens DATE|--milestone NAME|--off-track]
177
+ harbor sound TASK [DAYS] [--why TEXT] [--ask NAMES|crew] [--settle DAYS]
178
+ harbor soundings [PROJECT]
177
179
  harbor limit PROJECT [COLUMN N|none]
178
180
  harbor init [PROJECT] [--hook] [--dry-run] a project's tasks as files in this repository
179
181
  harbor init --local [NAME] a plan in this folder alone, no account
180
182
  harbor sync [--quiet] [--dry-run] the files and the website, in step both ways
181
183
  harbor handover PERSON [--to NAME] [--until DATE] [--note TEXT] [--keep ID,ID] [--confirm]
182
184
  harbor handback PERSON
185
+ harbor fog [--project P] [--list] tasks nobody has touched for three weeks, one at a time
186
+ harbor fog keep TASK it's still needed: out of the fog
183
187
  harbor agent [--agent NAME]
184
188
  harbor agent report TASK "WHAT YOU DID" [--start] [--agent NAME]
185
189
  ```
186
190
 
187
191
  `harbor handover Priya` lists everything Priya carries (open tasks, sign-offs waiting on her, risks and issues she owns, projects and programs she leads) and who should take each, from who has room this week. Nothing moves until you add `--confirm`. `--until DATE` is for time away: Priya shows as away on People, and `harbor handback Priya` gives back whatever is still with whoever took it. `--note` goes with each task and risk as a comment.
188
192
 
193
+ `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.
194
+
189
195
  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.
190
196
 
191
197
  `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.
192
198
 
193
- `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.
199
+ `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.
194
200
 
195
201
  `harbor brief --say` turns the brief into the BBC's Shipping Forecast: each program an area, wind for late work, visibility for health, gale warnings for anything off track. It prints the forecast and speaks it with your computer's own voice (`say` on a Mac, Windows' speech, or `espeak-ng` on Linux, which you may need to install). With `--json` it prints the forecast and stays quiet.
196
202