@pieerry/harness-kit 3.1.0 → 3.1.1

package/.claude/commands/product-manager/prd.md

@@ -30,4 +30,13 @@ Sensors: .claude/plugins/product-manager/sensors/prd-structure.md, .claude/plugi
 
 Evals: .claude/plugins/product-manager/evals/prd-quality.md, .claude/plugins/product-manager/evals/prd-readiness.md.
 
-After save reply: PRD saved at {path}. Score: {N}/10.
+After save, reply with this exact shape (name the actual sensors/evals/guides that ran, do not abbreviate):
+
+```
+PRD saved at {path}.
+  sensors: prd-structure ok, prd-acceptance-criteria ok
+  eval:    prd-quality {N}/10, prd-readiness {N}/10
+  guides:  product-guidelines.md, prd-guidelines.md, writing-style.md, templates/prd.md
+  refs:    business-info.md, squads/{squad}/context.md
+  next:    /product-manager:prp
+```

package/.claude/commands/product-manager/prp.md

@@ -34,4 +34,13 @@ Sensors: .claude/plugins/product-manager/sensors/prp-structure.md, .claude/plugi
 
 Evals: .claude/plugins/product-manager/evals/prp-quality.md, .claude/plugins/product-manager/evals/prp-context-readiness.md.
 
-After save reply: PRP saved at {path}. Score: {N}/10. Ready for handoff.
+After save, reply with this exact shape (name the actual sensors/evals/guides that ran):
+
+```
+PRP saved at {path}.
+  sensors: prp-structure ok, prp-context-quality ok, prp-links ok
+  eval:    prp-quality {N}/10, prp-context-readiness {N}/10
+  guides:  prp-guidelines.md, writing-style.md, templates/prp.md
+  refs:    prd/{feature_id}.md, {target repo paths probed}
+  next:    /sse:plan (ready for handoff)
+```

package/.claude/commands/product-manager/run.md

@@ -11,21 +11,27 @@ Run end to end.
 
 Follow .claude/plugins/product-manager/guides/pipeline.md. Read .claude/agents/product-manager.md for inputs and rules.
 
-Return format:
+Return format. Name every sensor, eval, and guide that ran. Generic summaries are not acceptable — list specifics so the user sees what was checked and what was loaded.
 
 ```
 Pipeline complete.
 
 PRD: .claude/plugins/product-manager/outputs/prd/{path}
-  sensors: passed (attempts: N)
-  eval: {score}/10
+  sensors: prd-structure ok, prd-acceptance-criteria ok ({sub-checks})
+  eval:    prd-quality {score}/10, prd-readiness {score}/10 (attempts: N)
+  guides:  product-guidelines.md, prd-guidelines.md, writing-style.md, templates/prd.md
+  refs:    business-info.md, squads/{squad}/context.md
 
 PRP: .claude/plugins/product-manager/outputs/prp/{path}
-  sensors: passed (attempts: N)
-  eval: {score}/10
+  sensors: prp-structure ok, prp-context-quality ok, prp-links ok
+  eval:    prp-quality {score}/10, prp-context-readiness {score}/10 (attempts: N)
+  guides:  prp-guidelines.md, writing-style.md, templates/prp.md
+  refs:    prd/{feature_id}.md, target repo paths probed
 
-Confluence: {published | skipped, reason}
+Confluence: {published to {space-key}: {url} | skipped, reason}
 
 Blockers:
 - {file:line, issue, fix}
 ```
+
+If a phase has no sensors/eval/guides/refs, omit that line rather than printing an empty one.

package/.claude/commands/sse/dev.md

@@ -46,4 +46,14 @@ Append approval marker when all gates pass:
 <!-- approved: {YYYY-MM-DD} -->
 ```
 
-Reply: Dev complete. {N} files changed, {M} commits. Next /sse:test.
+After approval, reply with this exact shape (name the actual sensors/guides that ran):
+
+```
+Dev complete. branch {branch}.
+  files changed: {N}
+  commits: {M} ({short-sha}, {short-sha}, ...)
+  sensors: code-conventions ok, test-coverage ok
+  guides:  coding-style.md, commit-style.md, skills/{area}/SKILL.md
+  refs:    plan/{feature_id}.md, conventions/{area}.md
+  next:    /sse:test
+```

package/.claude/commands/sse/plan.md

@@ -32,4 +32,13 @@ Sensors: .claude/plugins/staff-software-engineer/sensors/plan-structure.md.
 
 Evals: .claude/plugins/staff-software-engineer/evals/plan-quality.md.
 
-After save reply: Plan saved at {path}. Score: {N}/10.
+After save, reply with this exact shape (name the actual sensors/evals/guides that ran):
+
+```
+Plan saved at {path}.
+  sensors: plan-structure ok ({sub-checks: problem, files, gates, scope})
+  eval:    plan-quality {N}/10
+  guides:  pipeline.md, coding-style.md, skills/{area}/SKILL.md
+  refs:    prp/{feature_id}.md, conventions/{area}.md
+  next:    /sse:dev
+```

package/.claude/commands/sse/pr.md

@@ -42,4 +42,13 @@ Append approval marker:
 <!-- approved: {YYYY-MM-DD} ready-for-handoff: true -->
 ```
 
-Reply: PR opened: {url}.
+Reply with this exact shape:
+
+```
+PR opened: {url}
+  title:  {title}
+  draft:  {yes|no}
+  guides: pr-template.md, commit-style.md
+  refs:   plan/{feature_id}.md, dev/{feature_id}.md
+  next:   request review (if draft, mark ready when checks pass)
+```

package/.claude/commands/sse/run.md

@@ -12,28 +12,39 @@ Run end to end.
 
 Follow .claude/plugins/staff-software-engineer/guides/pipeline.md for retry, approval markers, token accounting, and publish behavior.
 
-Return format:
+Return format. Name every sensor, eval, and guide that ran. Generic summaries are not acceptable — list specifics so the user sees what was checked and what was loaded.
 
 ```
 Engineering pipeline complete.
 
 Plan: .claude/plugins/staff-software-engineer/outputs/plan/{path}
-  sensors: passed (attempts: N)
-  eval: {score}/10
+  sensors: {sensor-name} ok ({sub-check, sub-check, ...}), {sensor-name} ok
+  eval:    {eval-name} {score}/10 (attempts: N)
+  guides:  {guide-1.md}, {guide-2.md}, skills/{area}/SKILL.md
+  refs:    prp/{feature_id}.md, conventions/{area}.md
 
 Dev: branch {branch}
   files changed: N
-  commits: N
-  gates: code-style ok, conventions ok
+  commits: N ({short-sha}, {short-sha}, ...)
+  sensors: code-conventions ok, test-coverage ok
+  guides:  coding-style.md, commit-style.md, skills/{area}/SKILL.md
+  refs:    plan/{feature_id}.md, conventions/{area}.md
 
 Test: .claude/plugins/staff-software-engineer/outputs/test/{path}
-  passed: N, failed: M
+  command: {detected-test-command}
+  passed:  N, failed: M
+  duration: {seconds}s
 
 PR: {url}
+  title: {title}
   draft: yes|no
+  guides: pr-template.md, commit-style.md
+  refs:   plan/{feature_id}.md, dev/{feature_id}.md
 
-Confluence: {published | skipped, reason}
+Confluence: {published to {space-key}: {url} | skipped, reason}
 
 Blockers:
 - {file:line, issue, fix}
 ```
+
+If a phase has no sensors/eval/guides/refs, omit that line for that phase rather than printing an empty one.

package/.claude/commands/sse/test.md

@@ -37,4 +37,16 @@ Append approval marker when exit code is 0:
 
 If tests fail, return a blocker with the failing test names and a snippet of the failure output. Do not retry automatically; let the user decide.
 
-Reply: Tests {passed/failed}. {summary}.
+Reply with this exact shape:
+
+```
+Tests {passed|failed}.
+  command:  {detected-test-command}
+  passed:   {N}
+  failed:   {M}
+  duration: {seconds}s
+  output:   {path/to/test/output.md}
+  next:     /sse:pr (if passed) | fix failing tests (if failed)
+```
+
+If failed, append a `failures:` block listing each failing test name with a one-line snippet from the failure output.

package/README.md

@@ -5,7 +5,7 @@
 Claude Code harness for product + engineering delivery.
 From idea to merged PR, one pipeline.
 
-[![Version](https://img.shields.io/badge/version-3.1.0-blue.svg)](VERSION)
+[![Version](https://img.shields.io/badge/version-3.1.1-blue.svg)](VERSION)
 [![Claude Code](https://img.shields.io/badge/Claude%20Code-plugin-8b5cf6.svg)](https://claude.ai/code)
 [![Plugins](https://img.shields.io/badge/plugins-2-success.svg)](#layout)
 [![Pipeline](https://img.shields.io/badge/stages-6-informational.svg)](#usage)

package/VERSION

@@ -1 +1 @@
-3.1.0
+3.1.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pieerry/harness-kit",
-  "version": "3.1.0",
+  "version": "3.1.1",
   "description": "Claude Code harness for product + engineering delivery. From idea to merged PR, one pipeline.",
   "author": "Space Metrics AI",
   "license": "MIT",