feat(signoff): open the Check session with a jargon-free issue summary#255
Merged
Conversation
#245) When briefing the human for the Check beat, the sign-off session dived straight into gates and verdicts with no plain-language framing of what the change is about. Add a section to signoff.md instructing the agent to lead with a 2-3 sentence jargon-free summary — what was wrong in user terms and what the change does — analogous to the pr-description "User impact" opener, sourced from brief.md + patch.diff, before the §3-§6 walkthrough. It's a spoken briefing, not a new artifact, so the sign-off write boundary (exactly three things) is unchanged. Co-Authored-By: Claude Opus 4.8 (1M context) <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.
Closes #245.
Problem
When briefing the user for a Check beat, the system should generate a summary of the issue analogous to the PR introduction text — jargon-free and understandable without deep technical knowledge. Today the sign-off session goes straight into §3–§6 gates and verdicts with no plain-language framing.
Change
agents/signoff.md.jinjagains an "Open with a plain-language summary" section: the agent leads the session with a 2–3 sentence jargon-free summary — what was wrong (user terms, the symptom and who it hit) and what the change does — in the register of thepr-description.md"User impact" opener, sourced frombrief.md+patch.diff. Nopath:line/ type names / gate IDs. It is a spoken briefing, not a written artifact, so the sign-off write boundary ("exactly three things") is explicitly unchanged.Confirmed design: prompt-only (no new SUMMARY section, no assemble/leaf change). Single-source:
.claude/agents/signoff.md.jinja{% include %}s the body.Verification
cd template && make check— 478 driver unit tests pass.signoff.md.jinjaparses cleanly (jinja2).🤖 Generated with Claude Code