@pieerry/harness-kit 4.0.0 → 4.0.1
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 +56 -1
- package/VERSION +1 -1
- package/package.json +1 -1
- package/setup/install.sh +9 -9
package/README.md
CHANGED
|
@@ -4,7 +4,7 @@
|
|
|
4
4
|
|
|
5
5
|
From idea to merged PR. One pipeline. Six stages.
|
|
6
6
|
|
|
7
|
-
[](VERSION)
|
|
8
8
|
[](https://claude.ai/code)
|
|
9
9
|
[](#agents)
|
|
10
10
|
[](LICENSE)
|
|
@@ -51,6 +51,61 @@ CLI: `hk install` · `hk update` · `hk uninstall` · `hk status` · `hk version
|
|
|
51
51
|
|
|
52
52
|
---
|
|
53
53
|
|
|
54
|
+
## Getting started
|
|
55
|
+
|
|
56
|
+
Pick the flow that matches the task. All of them share the same pipeline state, so you can switch between them mid-feature.
|
|
57
|
+
|
|
58
|
+
### Big task — full pipeline (PM + Eng)
|
|
59
|
+
|
|
60
|
+
A new feature with stakes, ambiguity, or a Jira ticket attached. You want a written PRD, a thought-through PRP, a plan, code, tests, and a PR.
|
|
61
|
+
|
|
62
|
+
```
|
|
63
|
+
/product-manager:run # drafts PRD then PRP, with sensor + eval gates
|
|
64
|
+
/sse:run # plans, implements, tests, opens PR, watches for merge
|
|
65
|
+
```
|
|
66
|
+
|
|
67
|
+
Approve each artifact when prompted. The status bar tracks where you are in the six stages.
|
|
68
|
+
|
|
69
|
+
### Spec only — no code yet
|
|
70
|
+
|
|
71
|
+
You need the PRD and PRP to align with stakeholders before any engineering work. Stop after the PRP.
|
|
72
|
+
|
|
73
|
+
```
|
|
74
|
+
/product-manager:run
|
|
75
|
+
```
|
|
76
|
+
|
|
77
|
+
When eng is ready, hand them the repo and they run `/sse:run` against the approved PRP.
|
|
78
|
+
|
|
79
|
+
### Dev only — small change, plan in your head
|
|
80
|
+
|
|
81
|
+
A bug fix, a small enhancement, or a refactor where writing a PRD would be theatre. Skip PM, run engineering directly.
|
|
82
|
+
|
|
83
|
+
```
|
|
84
|
+
/sse:run # plan → dev → test → PR
|
|
85
|
+
```
|
|
86
|
+
|
|
87
|
+
Or run a single stage if that's all you need:
|
|
88
|
+
|
|
89
|
+
```
|
|
90
|
+
/sse:plan # just the plan
|
|
91
|
+
/sse:dev # just the code (against an approved plan)
|
|
92
|
+
/sse:test # just the tests
|
|
93
|
+
/sse:pr # just open the PR
|
|
94
|
+
```
|
|
95
|
+
|
|
96
|
+
### Resume — pick up where you left off
|
|
97
|
+
|
|
98
|
+
Closed the session, restarted Claude Code, or got interrupted. State persists at `.claude/.pipeline-state.json`.
|
|
99
|
+
|
|
100
|
+
```
|
|
101
|
+
/pipeline:continue # next pending stage for the active feature
|
|
102
|
+
/pipeline:reset # abandon the active run and start fresh
|
|
103
|
+
```
|
|
104
|
+
|
|
105
|
+
When the PR merges, the in-session monitor clears state automatically.
|
|
106
|
+
|
|
107
|
+
---
|
|
108
|
+
|
|
54
109
|
## Use it
|
|
55
110
|
|
|
56
111
|
```
|
package/VERSION
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
4.0.
|
|
1
|
+
4.0.1
|
package/package.json
CHANGED
package/setup/install.sh
CHANGED
|
@@ -61,17 +61,17 @@ mkdir -p "$TARGET/.claude/runtime/hooks" "$TARGET/.claude/runtime/scripts" "$TAR
|
|
|
61
61
|
for agent in product-manager staff-software-engineer; do
|
|
62
62
|
rm -rf "$TARGET/.claude/runtime/hooks/$agent"
|
|
63
63
|
cp -R "$SOURCE_ROOT/.claude/runtime/hooks/$agent" "$TARGET/.claude/runtime/hooks/$agent"
|
|
64
|
-
rm -rf "$TARGET/.claude/runtime/scripts/$agent"
|
|
65
|
-
cp -R "$SOURCE_ROOT/.claude/runtime/scripts/$agent" "$TARGET/.claude/runtime/scripts/$agent"
|
|
66
64
|
done
|
|
67
65
|
|
|
68
|
-
#
|
|
69
|
-
|
|
70
|
-
|
|
71
|
-
|
|
72
|
-
|
|
73
|
-
|
|
74
|
-
|
|
66
|
+
# PM scripts: copy real files. SSE scripts: build dir of symlinks → PM's shared utilities.
|
|
67
|
+
# (SSE scripts in source repo are symlinks; npm pack drops symlinks, so we recreate target-side.)
|
|
68
|
+
rm -rf "$TARGET/.claude/runtime/scripts/product-manager"
|
|
69
|
+
cp -R "$SOURCE_ROOT/.claude/runtime/scripts/product-manager" "$TARGET/.claude/runtime/scripts/product-manager"
|
|
70
|
+
|
|
71
|
+
rm -rf "$TARGET/.claude/runtime/scripts/staff-software-engineer"
|
|
72
|
+
mkdir -p "$TARGET/.claude/runtime/scripts/staff-software-engineer"
|
|
73
|
+
for name in sensor-runner.py token-phase.py; do
|
|
74
|
+
ln -sf "../product-manager/$name" "$TARGET/.claude/runtime/scripts/staff-software-engineer/$name"
|
|
75
75
|
done
|
|
76
76
|
|
|
77
77
|
# 4) Slash commands
|