@brainervirus/workit-cli 0.8.0 → 0.8.2
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 +7 -0
- package/assets/templates/execution-contract.md +11 -0
- package/assets/templates/superpowers-doc-contract.md +2 -0
- package/dist/index.js +2378 -147
- package/package.json +4 -4
package/README.md
CHANGED
|
@@ -20,6 +20,11 @@ npx @brainervirus/workit-cli init
|
|
|
20
20
|
workit init # interactive setup wizard
|
|
21
21
|
workit doctor # offline installation health report
|
|
22
22
|
workit doctor --json # machine-readable report
|
|
23
|
+
workit flow status --plan docs/<slug>/plan.md # read the effective flow state
|
|
24
|
+
workit flow pause --plan docs/<slug>/plan.md [--confirm] # active -> paused
|
|
25
|
+
workit flow resume --plan docs/<slug>/plan.md [--confirm] # paused -> active
|
|
26
|
+
workit flow complete --plan docs/<slug>/plan.md [--confirm] # complete (ledger + verification gated)
|
|
27
|
+
workit handoff --message "docs/<slug>/plan.md" # print the destination handoff prompt
|
|
23
28
|
workit # help
|
|
24
29
|
```
|
|
25
30
|
|
|
@@ -27,6 +32,8 @@ workit # help
|
|
|
27
32
|
|
|
28
33
|
`workit doctor` checks the offline installation health and exits nonzero when problems are found; `--json` prints the full report as JSON instead of the human-readable table.
|
|
29
34
|
|
|
35
|
+
`workit flow` maps the shared-core execution lifecycle (`pending`/`active`/`paused`/`completed`) to the CLI: `status` reads the effective flow state (approval digests, drift, execution, handoff-destination flag); `pause`/`resume`/`complete` mutate it with `--confirm` (or a TTY prompt when stdin is a TTY, exit 2 when neither applies). `workit handoff` prints the core destination handoff prompt (four-choice menu, never the originating Handoff option) and marks the flow as a handoff destination; a second handoff on an already-marked destination is rejected. Domain/verification failures exit 1 with structured JSON on stderr; usage errors exit 2.
|
|
36
|
+
|
|
30
37
|
## Behavior
|
|
31
38
|
|
|
32
39
|
- **Safe apply semantics** — a malformed `config.json` is detected before the wizard renders and reported as a friendly blocked output instead of crashing; the same guard runs after the Apply preview.
|
|
@@ -5,6 +5,17 @@ Load `using-superpowers`, `subagent-driven-development`, `test-driven-developmen
|
|
|
5
5
|
**Branch:** <BRANCH>
|
|
6
6
|
**SDD:** `<SDD_DIR>`
|
|
7
7
|
|
|
8
|
+
## Handoff destination
|
|
9
|
+
|
|
10
|
+
This session is a handoff destination for a continued plan. The originating session already recorded the post-plan menu choice; present exactly these four choices and never re-offer the originating handoff option:
|
|
11
|
+
|
|
12
|
+
- Subagent-driven
|
|
13
|
+
- Inline
|
|
14
|
+
- Review spec first
|
|
15
|
+
- Review plan first
|
|
16
|
+
|
|
17
|
+
<workflow-handoff-destination>true</workflow-handoff-destination>
|
|
18
|
+
|
|
8
19
|
## Hard gates
|
|
9
20
|
|
|
10
21
|
- The parent is coordinator-only: it does not edit product code or perform delegated exploration.
|
|
@@ -63,6 +63,8 @@ On success, use native `question` / Cursor `AskQuestion` with exactly these opti
|
|
|
63
63
|
|
|
64
64
|
Never emit Superpowers text beginning “Two execution options”.
|
|
65
65
|
|
|
66
|
+
A handoff destination session (the seeded contract carries `<workflow-handoff-destination>true</workflow-handoff-destination>`) presents exactly four choices — Subagent-driven, Inline, Review spec first, Review plan first — and never re-offers the originating handoff option.
|
|
67
|
+
|
|
66
68
|
- Specs/plans must follow `templates/spec-template.md` / `templates/plan-template.md` (mandated diagrams, tables, CA-XX).
|
|
67
69
|
|
|
68
70
|
## Doc delivery
|