Conversation
The generated perstack.toml definitions had recurring quality issues: bloated instructions full of code snippets, missing pick lists, no defaultModelTier, and flat delegation trees without cohesion rationale. Root cause: the knowledge about what makes a good instruction (defined in @create-expert/plan) was not reaching @create-expert/write-definition as actionable rules, and @create-expert/verify-test only checked test results, not definition quality itself. Changes to three delegates: - design-roles: add Delegation Tree Design section with software design principles (cohesion, coupling, information hiding); require pick lists and defaultModelTier in architecture output - write-definition: add Instruction Quality Rules (what belongs vs what does not — code snippets, general knowledge, procedures, file specs); add Description Rules (caller-facing); require delegation tree comment header; require explicit pick and defaultModelTier - verify-test: add Definition Quality Verification step that checks for bloated instructions, missing pick, missing modelTier, unjustified flat delegation, and procedural instructions — any violation triggers CONTINUE verdict for the build loop to fix Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Motivation
Generated definitions (e.g., bash-gaming) had recurring issues: instructions full of code snippets the LLM already knows, missing pick lists granting all tools, no defaultModelTier, and flat delegation trees without cohesion rationale. Root cause was that plan's knowledge about good instructions wasn't reaching write-definition as actionable rules, and verify-test only checked test results, not definition quality.
Test plan
npx perstack start create-expertwith the bash-gaming prompt and verify generated perstack.toml has concise domain-knowledge-only instructions, explicit pick lists, defaultModelTier on every expert, and delegation tree comment header🤖 Generated with Claude Code