copy: retire the withdrawn headline frame from the product and npm - #1226
Open
agents-squads[bot] wants to merge 1 commit into
Open
copy: retire the withdrawn headline frame from the product and npm#1226agents-squads[bot] wants to merge 1 commit into
agents-squads[bot] wants to merge 1 commit into
Conversation
Closes #1225 Founder direction 2026-08-13: never say the product replaces humans — the frame is "booting developers", capacity added to a person rather than headcount removed. Recorded in hq CLAUDE.md §Mission and _POSITIONING.md §Direction. The withdrawn frame was still shipping in user-facing output and, via package.json, on the public npm listing. Removed from all 23 occurrences: - Tagline (README, package.json, `squads --help`): "Boot AI teammates for the work you never get around to." PENDING founder sign-off before the next publish — the npm listing only refreshes on release, so nothing goes public until then. - In-product strings (`init` output, insights, `stats` header, the commit message `init` writes into the USER's repo): these need no frame at all, so they now state what happened — "your squads are ready". - Seed templates: these are copied into the user's own repository on `squads init`, so the frame was propagating into customer projects. - The two tests that asserted the banned string. Also fixes a real quickstart break introduced while editing: the README `mkdir`/`cd` pair had drifted apart (`mkdir my-workforce && cd my-squads`), which would have failed on a user's very first command. Co-Authored-By: Claude <noreply@anthropic.com>
|
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
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 #1225
Why
The headline frame withdrawn on 2026-07-30 was still shipping in user-facing output and, through
package.json, on the public npm listing. Founder direction 2026-08-13 tightens the rule: never say the product replaces humans — the frame is booting developers, capacity added to a person rather than headcount removed. Recorded in hqCLAUDE.md§Mission and_POSITIONING.md§Direction.What changed — two classes, deliberately separate
1. Tagline (README,
package.json,squads --help) — a positioning statement:This one needs your sign-off before the next publish. The npm description only refreshes on release, so nothing reaches the public listing until a release goes out — there is time to change it.
2. In-product strings — these need no frame at all, so they now state what happened rather than claiming anything:
squads initcompletioninitseed promptinitwrites into the user's repofeat: init agent squadsinsights.ts×4statsheaderSeed templates matter most here: they are copied into the user's own repository on
squads init, so the withdrawn frame was propagating into customer projects —CLAUDE.md.template,README.md.template, the demo squad, and the bundled skill.The two tests that asserted the banned string are updated in the same commit, since they would otherwise fail the moment it was removed.
A real bug caught on the way
The README quickstart had drifted to
mkdir my-workforce && cd my-squadsmid-edit — the two no longer agreed, which would fail on a user's first command. Fixed and the block re-read end to end.Verification
squads --helpfrom the built dist now shows the new line, andgrep -i "workforce"acrosssrc/,test/,templates/,docs/, README and package.json returns nothing.Full suite: 2558 pass. The 9 failures are pre-existing and unrelated — 8 in
test/commands/status.test.ts(uncommitted WIP addsbyTooltogetSessionSummarywithout updating the mock) and 1 from the #838 flaky cluster, which names a different test on each full-suite run and passes in isolation.🤖 Generated with Claude Code