Docs update: Remote Q&A scenario page - #318
Merged
bradygaster merged 1 commit intoMar 10, 2026
Merged
Conversation
Creates docs/src/content/docs/scenarios/remote-qa.md covering how to interact with Squad without cloning the repo locally. Documents three current paths (Copilot Chat, issue assignment, squad labels) and three future capabilities (branch-aware queries, Discussions integration, issue comment commands). Updates docs/src/navigation.ts to include the new scenario page. Closes bradygaster#314 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
diberry
commented
Mar 9, 2026
diberry
left a comment
diberry
left a comment
Contributor
Author
There was a problem hiding this comment.
✅ Approved — Clear, accurate, and well-structured.
Microsoft Style Guide compliance: ✅
- Sentence-case headings throughout
- Active voice and second person ("you")
- Present tense maintained
Technical accuracy: ✅
- Accurately describes current remote interaction paths (Copilot Chat, issue assignment, squad labels)
- Correctly notes limitations (default branch only, no branch-aware queries yet)
- Practical workarounds provided
Tone: ✅
- Matches Squad's pragmatic, no-hype voice
- "What's not supported yet" section is honest about gaps
- Tips section is actionable
Navigation: ✅
- Added to scenarios section in navigation.ts correctly
DOCS-TEST SYNC:
This PR adds a new scenario page but doesn't need test updates because the scenarios section uses dynamic discovery.
Minor suggestion (non-blocking):
Line 64: "and get branch-specific answers" has "d" prepended — looks like a typo. Should be "and get" not "and\r\nd get".
Great work on the comprehensive remote Q&A guide. This fills a real documentation gap.
— 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>
Contributor
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 new scenario page documenting how to interact with Squad remotely — without cloning the repo locally.
Changes
New:
docs/src/content/docs/scenarios/remote-qa.mdCovers three current remote interaction paths:
Documents three capabilities that don't exist yet:
/squad ask)Updated:
docs/src/navigation.tsAdded "Remote Q&A" entry to the Scenarios section.
Context
This scenario was identified during onboarding when exploring how to ask the squad questions from the GitHub browser without a local clone. Related to #260 (browser-native Squad exploration).
Closes #314
cc @bradygaster - cannot request reviewers from fork, requesting review via mention.