harness-everything 0.30.7 → 0.30.9

package/plugins/harness-everything/skills/grill-me/SKILL.md

@@ -1,43 +1,41 @@
 ---
 name: grill-me
-description: Acts as a relentless challenger to stress-test plans and architectures by interrogating one question at a time, finding loopholes, combating AI sycophancy, updating the CONTEXT.md glossary in real time, and handing off resolved decisions to to-spec for formal specs/ADRs.
+description: Stress-test plans and architectures one question at a time, expose blind spots, update domain terminology, and suggest an explicit to-spec handoff when alignment is complete.
 license: Apache-2.0
 metadata:
   author: Miya Daniel
-  version: 0.4.0
+  version: 0.30.8
 ---
 
-# Grill Me (Interrogation & Stress Testing)
+# Grill Me
 
-Stress-tests plans one question at a time, then hands off to `to-spec`.
+Stress-test a plan one question at a time.
 
 ## USE FOR:
-- Stress-test a vague plan or architecture proposal
-- Find loopholes and undefined boundary conditions pre-build
-- Combat AI sycophancy with adversarial questioning
-- Resolve decision-tree ambiguity before spec generation
+- vague plans or architecture proposals
+- adversarial design review
+- unresolved decision branches
 
 ## DO NOT USE FOR:
-- Implementing code or writing specs (`to-spec`, `tdd`)
-- Ticket breakdown of an approved spec (`to-tickets`)
-- Casual Q&A needing no adversarial challenge
+- implementation or spec publication
+- ticket decomposition
+- casual Q&A
 
 ## Skill Contract
 
 | Component | Specification |
 | :--- | :--- |
-| **Trigger / Input** | Vague plan proposal, "evaluate architecture", or explicit "grill me". |
-| **Expected Output** | Single-question interrogation loop resolving decision-tree branches; handoff to `to-spec` for spec/ADR generation. |
-| **State Mutations** | Updates `CONTEXT.md` glossary inline; delegates document creation to `to-spec`. |
-| **Enforcement Gate** | ONE question at a time; on consensus, invoke `to-spec` to preview & publish spec/ADR docs. |
+| **Trigger / Input** | Plan evaluation or explicit "grill me". |
+| **Expected Output** | Resolved decision tree plus explicit `/to-spec` handoff suggestion. |
+| **State Mutations** | May update `CONTEXT.md`; does not auto-run publication/ticket skills. |
+| **Enforcement Gate** | Ask ONE question at a time. Never auto-run `to-spec` or `to-tickets`. |
 
 ## Workflow
 
-1. [Discover] Scan plan-related code plus `<workspace>/CONTEXT.md`, `<workspace>/README.md`, ADRs under `<workspace>/docs/adr/`.
-2. Grill strictly using the project's domain model and terminology.
-3. Ask exactly ONE question at a time (questionnaires prohibited); attach your insight; resolve each branch before moving on.
-4. Update `CONTEXT.md` glossary inline as terms resolve.
-5. On consensus, hand off to `<skills-repo-root>/to-spec/SKILL.md` to preview the outline and publish (PRD, CLI/API reference, Schema doc, or ADR).
-6. Route execution: `to-tickets`, `fable-mode`, or `tdd`.
+1. Read relevant code, context, and ADRs.
+2. Challenge one branch at a time with project terminology.
+3. Update glossary terms as they resolve.
+4. On consensus, recommend explicit `/to-spec`.
+5. Suggest the next execution route without auto-invoking explicit-only skills.
 
 Deep dive: <this-skill-dir>/references/grilling-playbook.md

package/plugins/harness-everything/skills/grill-me/references/grilling-playbook.md

@@ -12,9 +12,9 @@ flowchart TD
     UpdateGlossary --> MoreBranches{3. Unresolved Decision Branches Remain?}
     
     MoreBranches -- Yes --> Loop
-    MoreBranches -- No (Consensus Reached) --> ToSpec[4. Hand off to to-spec for Outline Preview & Spec/ADR Publishing]
+    MoreBranches -- No (Consensus Reached) --> ToSpec[4. Recommend explicit /to-spec handoff]
     
-    ToSpec --> Execution[5. Route to to-tickets / fable-mode / tdd via harness-everything]
+    ToSpec --> Execution[5. Suggest /to-tickets / fable-mode / tdd as appropriate]
 ```
 
 ## 1. Persona: The Relentless Challenger
@@ -29,10 +29,10 @@ Your goal is to find loopholes, undefined boundary conditions, and potential per
 - **Rule of Single Question**: **You MUST only ask one question at a time**. Listing a long questionnaire with 5 questions is STRICTLY PROHIBITED.
 - **Tree Parsing**: Go deep down every branch of the decision tree. Only move to the next blind spot after resolving the current one.
 - **Provide Your Insight**: When asking a question, attach your professional insight.
-- **Real-time Glossary & Spec Handoff**: As domain terms and blind spots resolve, update `CONTEXT.md` (glossary) inline. Once the interrogation concludes with a full consensus, hand off to `to-spec` to preview the outline and publish the formal specification document (PRD, CLI/API reference, Schema doc, or ADR).
+- **Real-time Glossary & Spec Handoff**: As domain terms and blind spots resolve, update `CONTEXT.md` (glossary) inline. Once consensus is complete, recommend explicit `/to-spec`. Do not auto-run `to-spec` or `to-tickets`; publication remains behind their user-approval gates.
 
 ## 3. Exit Conditions and Handoff
 
 - Continue until you and the user reach a **"Shared Understanding with no suspense"**, and all branches of the decision tree are parsed and resolved.
-- **Handoff to Specification (`to-spec`)**: Once grilling concludes and all decision-tree branches are resolved, **MUST** hand off to `to-spec/SKILL.md` to synthesize the conversation into an outline preview and publish the corresponding document (PRD, CLI reference, Schema doc, or ADR) using `to-spec`'s path resolution flow.
-- **Handoff to Execution**: After `to-spec` publishes the specification, route to `to-tickets` (for ticket breakdown), `fable-mode` (for macro scaffolding), or `tdd` (for feature implementation).
+- **Specification suggestion (`/to-spec`)**: Once grilling concludes and all branches resolve, recommend explicit `/to-spec`. Only that explicit invocation may enter `to-spec/SKILL.md` and its preview/publication flow.
+- **Execution suggestion**: Suggest `/to-tickets`, `fable-mode`, or `tdd` as appropriate; do not auto-invoke explicit-only skills.

package/plugins/harness-everything/skills/grill-with-docs/SKILL.md

@@ -4,7 +4,7 @@ description: Challenge the plan against the existing domain model, sharpen termi
 license: Apache-2.0
 metadata:
   author: Miya Daniel
-  version: 0.12.0
+  version: 0.30.8
 ---
 
 # Grill With Docs (Domain Modeling & Architectural Alignment)
@@ -18,7 +18,7 @@ Interview the design tree one question at a time with recommended answers; explo
 | **Trigger / Input** | Stress-testing a plan against domain language and documented decisions. |
 | **Expected Output** | Structured interview; inline `CONTEXT.md` updates; ADR handoff. |
 | **State Mutations** | Writes the context glossary and ADRs at resolved locations. |
-| **Enforcement Gate** | Pure glossary; ADRs meet the 3-part bar; hand to `to-spec` after. |
+| **Enforcement Gate** | Pure glossary; ADRs meet the 3-part bar; suggest explicit `/to-spec` after alignment. Never auto-run `to-spec` or `to-tickets`. |
 
 ## Workflow
 
@@ -27,7 +27,7 @@ Interview the design tree one question at a time with recommended answers; explo
 3. Stress-test relationships with concrete scenarios; cross-check claims against code.
 4. Update the context glossary inline, never batch; zero implementation details.
 5. Offer an ADR only if hard to reverse + surprising without context + a real trade-off.
-6. Hand off unverified design to `grill-me`; aligned design to `to-spec`; execution to `to-tickets`/`fable-mode`/`tdd`.
+6. Hand off unverified design to `grill-me`; for aligned design suggest explicit `/to-spec`; for execution suggest `/to-tickets`, `fable-mode`, or `tdd` as appropriate without auto-invoking explicit-only skills.
 
 Deep dive: <this-skill-dir>/references/session-playbook.md
 

package/plugins/harness-everything/skills/grill-with-docs/references/session-playbook.md

@@ -22,9 +22,9 @@ flowchart TD
     WriteFallback --> CheckMore
 
     CheckMore -- Unresolved Branches Remain --> Frontier
-    CheckMore -- All Branches Resolved --> ToSpec[6. Hand off to to-spec for Outline Preview & Spec/ADR Publishing]
+    CheckMore -- All Branches Resolved --> ToSpec[6. Recommend explicit /to-spec handoff]
 
-    ToSpec --> Execution[7. Route to to-tickets / fable-mode / tdd via harness-everything]
+    ToSpec --> Execution[7. Suggest /to-tickets / fable-mode / tdd via harness-everything]
 ```
 
 ## Core interview prompt
@@ -95,5 +95,5 @@ If any of the three is missing, skip the ADR. Use the format in [ADR-FORMAT.md](
 
 1. **Pre-flight**: If the core proposal is highly vague or its technical robustness (SRE, security, locks, concurrency, fail-safes) is unverified, recommend the user run `grill-me` first. Do not attempt to align a glossary for a broken or unstable design.
 2. **Transition**: Once technical issues are hardened in `grill-me`, transition here to solidify domain terms and record architectural choices.
-3. **Downstream Specification Handoff**: Once alignment is complete and domain terms are updated, hand off to `to-spec/SKILL.md` to present an outline preview and publish the formal specification document or ADR.
-4. **Execution Handoff**: Route to `to-tickets` (for ticket decomposition), `fable-mode` (for macro scaffolding), or `tdd` (for feature implementation) via `harness-everything`.
+3. **Downstream Specification Suggestion**: Once alignment is complete, recommend explicit `/to-spec`. Do not auto-run `to-spec` or `to-tickets`; their approval gates remain authoritative.
+4. **Execution Suggestion**: Suggest `/to-tickets`, `fable-mode`, or `tdd` through `harness-everything` as appropriate.

package/sbom.cdx.json

@@ -2,23 +2,23 @@
   "$schema": "https://cyclonedx.org/schema/bom-1.7.schema.json",
   "bomFormat": "CycloneDX",
   "specVersion": "1.7",
-  "serialNumber": "urn:uuid:20a8a552-ae6f-558f-8a4b-07bc73059c4a",
+  "serialNumber": "urn:uuid:fdd6adf4-625c-5667-8d1c-1dd030c7b4a4",
   "version": 1,
   "metadata": {
-    "timestamp": "2026-10-07T02:50:57.855Z",
+    "timestamp": "2026-10-08T03:48:56.742Z",
     "tools": [
       {
         "vendor": "Harness Everything",
         "name": "generate-sbom.js",
-        "version": "0.30.7"
+        "version": "0.30.9"
       }
     ],
     "component": {
       "type": "application",
-      "bom-ref": "pkg:npm/harness-everything@0.30.7",
+      "bom-ref": "pkg:npm/harness-everything@0.30.9",
       "name": "harness-everything",
-      "version": "0.30.7",
-      "purl": "pkg:npm/harness-everything@0.30.7"
+      "version": "0.30.9",
+      "purl": "pkg:npm/harness-everything@0.30.9"
     }
   },
   "components": [
@@ -1999,7 +1999,7 @@
       ]
     },
     {
-      "ref": "pkg:npm/harness-everything@0.30.7",
+      "ref": "pkg:npm/harness-everything@0.30.9",
       "dependsOn": [
         "pkg:npm/%40commitlint/cli@19.8.1",
         "pkg:npm/%40commitlint/config-conventional@19.8.1",