Docs update: Add decision framework for when to add human members#317
Merged
bradygaster merged 1 commit intobradygaster:mainfrom Mar 10, 2026
Merged
Conversation
Adds a 'When to add a human member' section to the human team members feature page with a decision table, litmus test, and note about automatic identification via git config. Also adds a cross-reference link from the your-team concept page to the new decision framework section. Closes bradygaster#313 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
diberry
commented
Mar 9, 2026
Collaborator
Author
diberry
left a comment
diberry
left a comment
There was a problem hiding this comment.
✅ Approved — Excellent decision framework addition.
Microsoft Style Guide compliance: ✅
- Sentence-case heading: "When to add a human member"
- Active voice throughout
- Second person ("you") consistently used
- Present tense maintained
Technical accuracy: ✅
- Decision table is practical and actionable
- Litmus test is clear: "stop and wait" vs. async GitHub flows
- Correctly distinguishes roster members from normal collaborators
- Cross-link from your-team.md is appropriate and helpful
Tone: ✅
- Clear, pragmatic, no handwaving
- Directly addresses a common question ("should I add this person?")
- The git config user.name clarification is helpful
Navigation: ✅
- No nav changes needed (editing existing pages)
- Cross-link correctly references relative path
DOCS-TEST SYNC: ✅ Not required
This PR edits existing pages, doesn't add new ones. No test updates needed.
Great addition. This will save teams from over-engineering their rosters.
— PAO
diberry
added a commit
to diberry/squad
that referenced
this pull request
Mar 9, 2026
… recommendations Session: 2026-03-09T19-16-49Z-docs-consolidation Requested by: Copilot (Scribe role) Changes: - Merged 5 inbox decisions (user directives, McManus docs audit, Keaton config audit) - Updated decisions.md with progressive disclosure framework and docs work classification - Appended cross-agent team updates to PAO, FIDO, Procedures history files - Cleared decision inbox (5 files removed) Summary: - PAO approved all 4 docs PRs (bradygaster#318, bradygaster#317, bradygaster#305, bradygaster#303) with docs-test sync verified - FIDO validated test assertions for 4 new docs files (EXPECTED_CONCEPTS array correct, no gaps) - Procedures approved human-members.md template PR bradygaster#315 - 44-issue docs backlog now configured with routing, ceremonies, skills, and @copilot capability profile - Team aligned on progressive disclosure and documentation conventions Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Collaborator
Author
|
@bradygaster — This PR is ready for your review. CI is green. 🚀 |
Ab3y
pushed a commit
to Ab3y/squad
that referenced
this pull request
Mar 10, 2026
…adygaster#316-bradygaster#322) - Map short event names to SDK dotted-namespace names (assistant.message_delta, etc.) - Normalize event.data payloads to flat SquadSessionEvent shape - Replace all unsafe as-unknown-as casts with explicit field mapping - Type client event handlers with SquadClientEventType generics - Add sendAndWait(), abort(), getMessages() adapter methods - Remove dead _squadOnMessage reference - 19 adapter tests (up from 9), 2219 total tests passing Closes bradygaster#316, bradygaster#317, bradygaster#318, bradygaster#319, bradygaster#320, bradygaster#321, bradygaster#322 Credit to @spboyer for surfacing adapter patterns in the original beta Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.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
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.
Summary
Adds a decision framework to help users understand when to add someone as a human team member versus leaving them as a normal GitHub collaborator.
Changes
docs/src/content/docs/features/human-team-members.mdgit config user.namedocs/src/content/docs/concepts/your-team.mdWhy
The existing docs explain how to add human members (mechanics, pausing, routing) but not when or why. New users don't have a clear signal for the decision. This was identified during onboarding.
Closes #313
cc @bradygaster - cannot request reviewers from fork, requesting review via mention.