prompts(kit, scout): add @-mention discipline section#506
Merged
Conversation
`@scout` / `@kit` are tool calls — the ping fires the instant the
message sends — but the existing rules ("only at handoff points",
"only when starting a new assignment") were buried in workflow and
communication sections, stated as etiquette, and had no examples.
Models still narrate intent ("…and pulling in @scout for plan
review…"), which fires the ping before any real assignment exists.
Add a top-level "@-Mention Discipline" section to both built-ins
that frames `@` as a mechanical trigger, with concrete WRONG/RIGHT
examples mirroring the failure mode. Soften the existing scattered
rules to point at the new section rather than restate it.
Custom personas (Rick crew) get the same treatment in the live
store; this commit covers the built-ins so the discipline ships
to all Sprout users in the next build.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This was referenced May 28, 2026
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
# @-Mention Disciplinesection to Kit's and Scout's system prompts that frames@as a mechanical trigger ("typing@scoutfires a ping the instant the message sends — there is no pre-mention"), with concrete WRONG/RIGHT examples.@-mention rules in workflow / communication sections to point at the new section rather than restate it.Why
PR #499 introduced messaging-discipline rules but stated them as etiquette ("only at handoff points"), buried in Communication sections, with no examples. Models still narrate intent ("…and pulling in @scout for plan review…") which fires the ping before any real assignment exists. See screenshot in the linked discussion: Rick narrating "pulling in @meeseeks to research" caused Meeseeks to respond enthusiastically before any brief was provided.
The fix reframes the rule from etiquette → mechanics ("
@is a tool call"), promotes it to a top-level section, and shows concrete wrong/right examples mirroring the failure mode.Scope
This PR covers the built-in personas (Kit, Scout). Custom personas (Rick & co.) get the same treatment in the local persona store; that's a per-user setting, not a code change.
Test plan
@scoutreference@s Scout when delivering an actual assignment with PHASE/worktree/deliverable@kitreference;@kitonly appears on the final report or a specific blocker🤖 Generated with Claude Code