docs(spec): SKILL brain structure — mode-based vs connector-based (direction proposal)#156
Open
jordanrburger wants to merge 1 commit into
Open
docs(spec): SKILL brain structure — mode-based vs connector-based (direction proposal)#156jordanrburger wants to merge 1 commit into
jordanrburger wants to merge 1 commit into
Conversation
…rection proposal) A direction-setting proposal (for review by others, not yet decided) on whether SKILL.md should canonically use the mode-based structure (a running vault today) or the connector-based structure (the engine today), and the migration path either way. Genuinely open evaluation across six criteria, weighted toward vault<->engine convergence, self-improvement-loop fit, and distributability (legibility explicitly de-prioritized). The analysis recommends connector-based — it ends the recurring merge tax by construction and is the shape the modular self-improvement loop and the optional-connector catalog are built for; the honest cost is human legibility, flagged for reviewers to challenge. Migration strategy is upstream-first (finish porting the vault's ~24 Patterns + capabilities into the engine's connector phases, then the vault re-renders and adopts — no risky local re-graft), gated by a completeness checklist + behavioral dry-run validation so nothing is lost. Out of scope: implementation (the remaining upstream PRs + the Phase-2 adoption/validation harness) follows once the direction is agreed. Companion to specs #149/#150/#152. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Jun 23, 2026
Merged
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.
Direction-setting proposal — for review, no decision baked in and no implementation here. This sets the long-term shape of how every Scout instance's brain is organized, so it's deliberately up for debate. Companion to #149/#150/#152.
The fork
Scout has two brains that diverged in structure: a running vault's
SKILL.mdis mode-based (organized by run mode), the engine is connector-based (per-connector sections + a Run Modes dispatch table). They don't match, so every/scout-updatethat touches the brain throws a merge conflict, and the regenerated runner references a "Run Modes table" the mode-based brain lacks. Worth settling deliberately.What the proposal does
Asking reviewers
Spec:
docs/superpowers/specs/2026-06-22-skill-brain-structure-direction-design.md🤖 Generated with Claude Code