Skip to content

docs: Add Squad overview and comprehensive installation guide#1453

Open
ElazarK wants to merge 1 commit into
bradygaster:devfrom
ElazarK:add-squad-overview-and-install-docs
Open

docs: Add Squad overview and comprehensive installation guide#1453
ElazarK wants to merge 1 commit into
bradygaster:devfrom
ElazarK:add-squad-overview-and-install-docs

Conversation

@ElazarK

@ElazarK ElazarK commented Jul 6, 2026

Copy link
Copy Markdown

This PR adds two new documentation articles to the Squad docs:

What's included

  • what-is-squad.md (concepts/) — Comprehensive overview explaining Squad architecture, capabilities, workflow, and governance
  • install-comprehensive.md (get-started/) — Step-by-step installation guide covering CLI, VS Code, and SDK installation paths, plus troubleshooting

Key features

  • Architecture system diagram and component explanations (Coordinator, Agents, Memory, Routing, Scribe, Ralph)
  • Three installation paths (CLI, VS Code, SDK) with clear prerequisites
  • Troubleshooting section for common setup issues
  • Optional sections for personal squad and typed configuration
  • Adapted to Astro docs format and structure

Both articles provide thorough setup guidance for new Squad users.

- Add what-is-squad.md in concepts/ with detailed feature overview, architecture, and workflow explanation
- Add install-comprehensive.md in get-started/ with step-by-step CLI, VS Code, and SDK installation paths
- Both articles include prerequisites, troubleshooting, and optional advanced setup sections
- Format adapted for Astro docs structure

Co-authored-by: Elazar Krieger <elkrieger@microsoft.com>
Copilot AI review requested due to automatic review settings July 6, 2026 15:54
@github-actions

github-actions Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

🟢 Impact Analysis — PR #1453

Risk tier: 🟢 LOW

📊 Summary

Metric Count
Files changed 2
Files added 2
Files modified 0
Files deleted 0
Modules touched 1

🎯 Risk Factors

  • 2 files changed (≤5 → LOW)
  • 1 module(s) touched (≤1 → LOW)

📦 Modules Affected

docs (2 files)
  • docs/src/content/docs/concepts/what-is-squad.md
  • docs/src/content/docs/get-started/install-comprehensive.md

This report is generated automatically for every PR. See #733 for details.

@github-actions

github-actions Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

🛫 PR Readiness Check

ℹ️ This comment updates on each push. Last checked: commit 62015d1

PR Scope: 🔧 Infrastructure

⚠️ 2 item(s) to address before review

Status Check Details
Single commit 1 commit — clean history
Not in draft Ready for review
Branch up to date Up to date with dev
Copilot review No Copilot review yet — it may still be processing
Changeset present No source files changed — changeset not required
Scope clean No .squad/ or docs/proposals/ files
No merge conflicts No merge conflicts
Copilot threads resolved No Copilot review threads
CI passing 6 check(s) still running

Files Changed (2 files, +336 −0)

File +/−
docs/src/content/docs/concepts/what-is-squad.md +129 −0
docs/src/content/docs/get-started/install-comprehensive.md +207 −0

Total: +336 −0


This check runs automatically on every push. Fix any ❌ items and push again.
See CONTRIBUTING.md and PR Requirements for details.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds two new documentation pages to the Astro docs site: a conceptual overview of Squad (architecture/capabilities) and a comprehensive installation guide covering CLI/VS Code/SDK paths plus troubleshooting.

Changes:

  • Add a new “What is Squad?” concepts article describing core components, workflow, and governance.
  • Add a new “Installation (comprehensive)” get-started guide covering install/update/init/validation and optional personal squad + typed config.
  • Include onboarding-friendly sections like troubleshooting and cross-project personal squad setup.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 6 comments.

File Description
docs/src/content/docs/get-started/install-comprehensive.md New installation guide; currently contains several correctness issues (Node version requirement, npx usage, personal squad path, typed config example, stale expected output).
docs/src/content/docs/concepts/what-is-squad.md New conceptual overview; one claim about memory persistence “across branches” is misleading given .squad/ is typically git-tracked and branch-specific.

Comment on lines +11 to +13
- **[Node.js 20 or later](https://nodejs.org/en/download)** — verify by running `node --version`
- **[A Git repository](https://git-scm.com/)** (new or existing)
- **[GitHub Copilot](https://github.com/features/copilot)** — required for the VS Code agent workflow
squad status
```

You can also use `npx squad status` if you skipped the global install.
Comment on lines +148 to +154
Squad writes the personal configuration to a platform-specific path:

| Platform | Path |
| --- | --- |
| Linux | `~/.config/squad/` |
| macOS | `~/Library/Application Support/squad/` |
| Windows | `%APPDATA%\squad\` |
Comment on lines +160 to +170
```typescript
import { defineConfig } from '@bradygaster/squad-sdk';

export default defineConfig({
agents: {
dir: '.github/agents',
},
squad: {
dir: '.squad',
},
});
Comment on lines +21 to +24
### Persistent memory across sessions

Each agent writes its working state to `.squad/agents/`. Memory persists between VS Code sessions, across branches, and across team members. An agent that reviewed a pull request yesterday remembers the context when it picks up the follow-on task today.

Comment on lines +108 to +116
**Expected output:**

```
✅ Squad installed.
.github/agents/squad.agent.md — coordinator agent
.squad/templates/ — 11 template files

Open GitHub Copilot and select Squad from the agent list.
```

@tamirdresher tamirdresher left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice docs addition. A few things to fix before merge:

  • Broken internal link in the overview page.
  • npm bin -g is deprecated in npm 9+ — recommend replacing with the current equivalent.
  • The governance section overstates enforcement guarantees relative to how Squad actually behaves; suggest softening the wording for public docs.

@tamirdresher

Copy link
Copy Markdown
Collaborator

Thanks for putting this together, @ElazarK — the two new pages fill a real gap and read well. Consolidating my earlier review plus Copilot's inline notes into one ask so you have a single revision list. All items are confirmed against dev at commit 62015d1:

docs/src/content/docs/get-started/install-comprehensive.md

  1. Node prerequisite (line 11) — both @bradygaster/squad-cli and @bradygaster/squad-sdk declare "engines": { "node": ">=22.5.0" } in dev. Please update from "Node.js 20 or later" so Node 20 users don't hit install/execute failures.
  2. npx example (line 128) — npx squad status won't resolve the CLI package. Please match the pattern used earlier in the page: npx @bradygaster/squad-cli status.
  3. Personal squad path (lines 150–154) — the table currently lists the container directory. The actual personal squad root is the personal-squad/ subdirectory inside it (see packages/squad-cli/src/cli/commands/personal.ts and packages/squad-sdk/src/resolution.ts). Please append /personal-squad/ to each row (e.g. ~/.config/squad/personal-squad/).
  4. Typed config example (lines 160–171) — defineConfig() in packages/squad-sdk/src/config/schema.ts expects top-level team, routing, models, and an agents array; agents.dir / squad.dir aren't part of the schema and won't validate. Please replace the snippet with a minimal shape that matches SquadConfig.
  5. Expected output block (lines 110–116) — the current squad init output no longer prints "11 template files". To keep this from going stale, please either capture the current output verbatim or replace with an abbreviated illustrative summary and a note that output may vary between versions.
  6. npm bin -g in Troubleshoot (lines 182 and 188) — this was removed in npm 9. Please swap for the current equivalent, e.g. export PATH="$(npm prefix -g)/bin:$PATH" on macOS/Linux and the corresponding $(npm prefix -g) on Windows (or npm config get prefix).

docs/src/content/docs/concepts/what-is-squad.md

  1. Branch-memory wording (line 23) — since .squad/ is committed to the repo, its contents change with the branch. Please reframe from "across branches" to persistence across sessions / team members via version control (and optionally via a personal squad).
  2. Broken internal link (line 54) — /docs/get-started/installation/ skips the site's base: '/squad/' prefix and 404s in production. Please switch to the relative form other docs use (../get-started/installation) or the fully prefixed /squad/docs/get-started/installation/.
  3. Governance section (lines 29–36) — the "File-write guards / PII scrubbing / Reviewer lockout / Escalation points" bullets read as hard framework-enforced guarantees, which overstates what Squad actually enforces at runtime today (these live largely as templates and conventions). For a public overview, please soften to something like "Squad ships templates and conventions that help teams enforce…" and make the human-in-the-loop framing the primary claim.

Could you push one focused revision covering these items and I'll re-review right away? Really appreciate the contribution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants