Docs: Scenario — Remote Q&A with Squad (no local clone) #314

Scenario

A contributor wants to ask questions of their Squad from the browser — without cloning the repo locally. Answers should be branch-aware, defaulting to main if no branch is specified.

User story

As a squad user, I want to ask my team questions from GitHub.com (or another remote interface) so that I can get branch-specific answers without setting up a local environment.

Current state

Closest existing path

Copilot Chat on github.com is the lowest-effort option — squad.agent.md already exists (1,066 lines of governance). If Copilot is enabled on the repo, a user can open a chat session scoped to any branch and ask questions. The gap is enabling it and documenting the workflow.

What this scenario doc should cover

1. Three approaches (ranked by effort):

   • Copilot Chat — open github.com, start chat, reference squad agent, ask questions scoped to a branch
   • GitHub Discussions + workflow — post a discussion with optional branch: feature-xyz in the body → workflow fires, responds as comment
   • Issue comment commands — comment @squad what does X do? on any issue → workflow parses and responds

2. Branch specification pattern — how users indicate which branch (label, body text, default to main)

3. What works today vs. what needs to be built — honest assessment of each approach

4. Limitations — what remote Q&A can't do (e.g., no local file system access, no real-time agent spawning from browser)

Related

• Issue Explore: GitHub.com-based Squad experience #260 — exploring full browser-native Squad experience
• squad-issue-assign.yml line ~127 — hard-coded default_branch

Acceptance criteria

• Scenario doc at docs/src/content/docs/scenarios/remote-qa.md
• Covers all three approaches with pros/cons
• Includes branch-awareness pattern
• Links to related issues and existing workflows