arggon-harness 0.2.1 → 0.2.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.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/src/agents/spec-verify.md +12 -7
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "arggon-harness",
3
- "version": "0.2.1",
3
+ "version": "0.2.2",
4
4
  "description": "Spec-driven SDLC workflow for OpenCode — plugin, skills, commands, and init system",
5
5
  "type": "module",
6
6
  "main": "dist/plugin/index.js",
package/src/agents/spec-verify.md CHANGED
@@ -7,6 +7,7 @@ permission:
7
7
  glob: allow
8
8
  grep: allow
9
9
  spec_change_list: allow
10
+ spec_change_status: allow
10
11
  spec_verify: allow
11
12
  spec_integrity_check: allow
12
13
  write: deny
@@ -59,7 +60,8 @@ Run 5-dimension verification on a spec change.
59
60
  - Read spec/config.yaml for project context
60
61
 
61
62
  2. **Run verification**
62
- - Call `spec_verify` with change name
63
+ - Call the `spec_verify` tool with the change name (this runs all 5 dimensions server-side)
64
+ - Do NOT attempt to run tests or commands via bash — the tool handles test execution
63
65
  - Optionally specify dimensions (default: all)
64
66
 
65
67
  3. **Show report**
@@ -76,7 +78,7 @@ Run 5-dimension verification on a spec change.
76
78
  - For CRITICAL issues: must fix before archive
77
79
  - For WARNINGs: should fix, but not blocking
78
80
  - For SUGGESTIONs: nice to fix
79
- - Offer to help fix issues
81
+ - Offer to help fix issues (use read/grep to investigate — not bash)
80
82
 
81
83
  5. **Re-verify**
82
84
  - After fixes, run verification again
@@ -88,11 +90,11 @@ Run 5-dimension verification on a spec change.
88
90
 
89
91
  ## Verification Heuristics
90
92
 
91
- - **Integrity**: Hash comparison, field validation
92
- - **Compliance**: Grep for requirement IDs in code, check test files
93
- - **Tasks**: Parse task status, check git diff for changes
94
- - **Coherence**: Extract design decisions, search for patterns
95
- - **Regression**: Compare delta specs with main specs
93
+ - **Integrity**: Call `spec_integrity_check` tool — it handles hash comparison and field validation server-side
94
+ - **Compliance**: Use `grep` tool to find requirement IDs in source files; use `read` to check test files
95
+ - **Tasks**: Call `spec_task_progress` to get task completion status; use `read` to verify affected files exist
96
+ - **Coherence**: Use `read` to extract design decisions from design-tech.yaml; use `grep` to search for implementation patterns
97
+ - **Regression**: Use `read` to compare delta specs with main specs; no command execution needed
96
98
 
97
99
  ## Guardrails
98
100
 
@@ -101,3 +103,6 @@ Run 5-dimension verification on a spec change.
101
103
  - Every issue must have actionable recommendation
102
104
  - Include file/line references
103
105
  - Note which checks were skipped and why
106
+ - Do NOT attempt to run tests, commands, or git operations via bash — use read/grep/glob for file checks
107
+ - The spec_verify tool handles all verification server-side (integrity, test execution, compliance)
108
+ - If you need to check something not covered by the tool, use read/grep/glob — never bash