From 3d995cd1f0818f3a7711655fbc8b26c2e9783ab6 Mon Sep 17 00:00:00 2001 From: HiranoMasaaki Date: Fri, 13 Mar 2026 22:37:00 +0000 Subject: [PATCH 1/2] fix: make review-definition checklist concrete with domain-neutral violation patterns MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Reviewer was passing perstack.toml with file paths, Deliverables sections, internal API names, and implementation details because the checklist was too abstract ("contains only domain constraints"). Add specific flag criteria: - Output locations/structure (where to place results, artifact enumeration) - Internal APIs of specified tools (methods/hooks/functions — derivable) - Named alternatives to reject (implicit from positive specification) - Implementation approach (how vs what) - Code snippets, data schemas, step-by-step procedures All patterns are domain-neutral per Design Principle 3 (Domain Agnosticism). Co-Authored-By: Claude Opus 4.6 (1M context) --- definitions/create-expert/perstack.toml | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/definitions/create-expert/perstack.toml b/definitions/create-expert/perstack.toml index e3bc5720..728b891d 100644 --- a/definitions/create-expert/perstack.toml +++ b/definitions/create-expert/perstack.toml @@ -402,9 +402,12 @@ For library/tool names appearing in any instruction: - Traceable to plan.md's Domain Knowledge (i.e., user-specified)? (✓/✗ per name) - If not user-specified, flag it — the instruction should describe the capability, not name the tool. -For each non-coordinator instruction: -- Contains only domain constraints the LLM cannot derive on its own? (✓/✗) -- Free of code snippets, JSON schemas, and step-by-step procedures? (✓/✗) +For each non-coordinator instruction, flag (✗) if any of the following appear: +- Output locations or structure — dictates where to place results or enumerates specific artifacts to produce. The instruction should describe what the output must accomplish, not its shape. +- Internal APIs of specified tools — names specific methods, hooks, functions, or parameters of a tool. "Use tool X" is the constraint; how to use its API is derivable. +- Named alternatives to reject — lists tools or approaches NOT to use. Specifying what to use implicitly excludes alternatives. +- Implementation approach — describes how to build something rather than what constraints the result must satisfy. +- Code snippets, data schemas, or step-by-step procedures. ## Verdicts From 5e52e9d18a5677afd3fae01046a884ae249a048b Mon Sep 17 00:00:00 2001 From: HiranoMasaaki Date: Fri, 13 Mar 2026 22:39:53 +0000 Subject: [PATCH 2/2] chore: bump create-expert version to 1.0.18 Co-Authored-By: Claude Opus 4.6 (1M context) --- definitions/create-expert/perstack.toml | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/definitions/create-expert/perstack.toml b/definitions/create-expert/perstack.toml index 728b891d..5c7592ae 100644 --- a/definitions/create-expert/perstack.toml +++ b/definitions/create-expert/perstack.toml @@ -88,7 +88,7 @@ [experts."create-expert"] defaultModelTier = "high" -version = "1.0.17" +version = "1.0.18" description = "Creates and modifies Perstack expert definitions in perstack.toml" instruction = """ You are the coordinator for creating and modifying Perstack expert definitions. perstack.toml is the single source of truth — your job is to produce or modify it according to the user's request. @@ -133,7 +133,7 @@ pick = ["readTextFile", "exec", "attemptCompletion"] [experts."@create-expert/plan"] defaultModelTier = "high" -version = "1.0.17" +version = "1.0.18" description = """ Analyzes the user's request and produces plan.md: domain constraints, test query, verification signals, and role architecture. Provide: (1) what the expert should do, (2) path to existing perstack.toml if one exists. @@ -220,7 +220,7 @@ pick = [ [experts."@create-expert/build"] defaultModelTier = "low" -version = "1.0.17" +version = "1.0.18" description = """ Orchestrates the write → review → test → verify cycle for perstack.toml. Provide: path to plan.md (containing requirements, architecture, test query, and verification signals). @@ -278,7 +278,7 @@ pick = ["readTextFile", "exec", "todo", "attemptCompletion"] [experts."@create-expert/write-definition"] defaultModelTier = "low" -version = "1.0.17" +version = "1.0.18" description = """ Writes or modifies a perstack.toml definition from plan.md requirements and architecture. Provide: (1) path to plan.md, (2) optionally path to existing perstack.toml to preserve, (3) optionally feedback from a failed test to address. @@ -381,7 +381,7 @@ pick = [ [experts."@create-expert/review-definition"] defaultModelTier = "low" -version = "1.0.17" +version = "1.0.18" description = """ Reviews perstack.toml against plan.md for domain knowledge alignment and instruction quality. Provide: (1) path to plan.md, (2) path to perstack.toml. @@ -430,7 +430,7 @@ pick = ["readTextFile", "todo", "attemptCompletion"] [experts."@create-expert/verify-test"] defaultModelTier = "low" -version = "1.0.17" +version = "1.0.18" description = """ Executes hard signal checks against test-expert's results, verifies their reproducibility, and checks the definition structure. Provide: (1) the test-expert's factual report (query, what was produced, errors), (2) the verification signals from plan.md, (3) path to perstack.toml. @@ -493,7 +493,7 @@ pick = ["readTextFile", "exec", "todo", "attemptCompletion"] [experts."@create-expert/test-expert"] defaultModelTier = "low" -version = "1.0.17" +version = "1.0.18" description = """ Executes a single test query against a Perstack expert definition and reports what happened. Provide: (1) path to perstack.toml, (2) the test query to execute, (3) the coordinator expert name to test.