Skip to content

docs: add .squad directory explainer to first-session guide #290

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
diberry wants to merge 1 commit into from
Closed

docs: add .squad directory explainer to first-session guide #290

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 19 additions & 1 deletion docs/get-started/first-session.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,25 @@ Say "yes" or skip straight to a task (which is implicit confirmation):
> Yes. Dallas, set up the Express server with basic routing.
```

Squad creates the `.squad/` directory structure — team roster, routing rules, casting state, ceremony config, agent charters, and histories — all seeded with your project context. Then it spawns Dallas:
Squad creates the `.squad/` directory structure — team roster, routing rules, casting state, ceremony config, agent charters, and histories — all seeded with your project context.

### What's inside .squad/?

| File/Directory | Purpose |
|---|---|
| `team.md` | Team roster, roles, and member info |
| `routing.md` | Work routing rules (which agent handles what) |
| `decisions.md` | Team decisions — all agents read this before working |
| `agents/` | Each agent's charter and history (their memory) |
| `ceremonies.md` | Ceremony schedule (retrospectives, reviews, etc.) |
| `casting/` | Team formation history and casting state |
| `skills/` | Reusable capabilities agents can learn |

**You own these files.** Edit them anytime — change roles, add routing rules, fix decisions. Squad reads them before every spawn.

**Commit `.squad/` to version control.** It's your team's brain. Anyone who clones the repo gets the team with all their knowledge.

Then it spawns Dallas:

```
🔧 Dallas — setting up Express server with routing
Expand Down