Repository navigation
thread tool: initial_message IS the build brief - #52
Merged
Merged
Conversation
Two spun-out build threads (2026-09-13) got brief-less seeds: the parent session templated 'EXECUTION APPROACH' boilerplate instead of the actual build request, and one thread session then created a *duplicate* thread to fix its own thin seed. Make the tool description + initial_message param say it plainly: seed with the goal and deliverable first; no generic execution template.
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
2 participants
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.
Problem
On 2026-09-13, a parent session spun out two build threads (
build-mosquitonets-org,build-midicontroller-net) whose seed messages were all execution-approach boilerplate and no actual brief ("EXECUTION APPROACH: PLAN FIRST…" with the goal buried at the bottom). One of the thread sessions thenthread-called its way out of the thin seed, creating a duplicate thread with the real brief a minute later.Fix
Make the tool speak plainly:
initial_messageis the build brief. Tool description now says to open with the concrete goal and deliverable, not a generic execution template; the param description says the same for the seed.Companion change: pollux repo d8a2000 restructures the planning skill's thread-handoff template to brief-first.