Benefit-first communication pass across README, docs, and descriptions - #31
Merged
Conversation
Reframe user-facing text to lead with the problem solved (forgotten companion changes) instead of the mechanism (change coupling, mining): - README: new benefit-first opening, define "hole" on first use, add a plain-text sample of check output, rewrite demo captions - docs: same captions, one-line hole definition under the title; research/threshold sections unchanged - NuGet Description, CLI --help header, and MCP registry description rewritten benefit-first Co-Authored-By: Claude Fable 5 <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.
What
Reframes all user-facing text to lead with the problem the tool solves (forgotten companion changes) instead of the mechanism (change coupling, repository mining). No behavior changes.
checkoutput, and rewrites the demo captions to describe what each screenshot shows.<Description>, CLI--helpheader, and MCP registry description (.mcp/server.json): rewritten benefit-first; tags unchanged.Why
First-time visitors were greeted with field jargon ("the free, agent-native slice of change coupling") before learning what the tool does for them. The change-coupling framing stays in docs where it earns its keep with tech leads; the front page now sells the outcome.
The
mcp-nameregistry marker in README is untouched.🤖 Generated with Claude Code