
Shared hard rules enforced across all squad agents
Defensive CI/CD patterns: semver validation, token checks, retry logic, draft detection — earned from v0.8.22
Microsoft Style Guide + Squad-specific documentation patterns
Coordinating work across multiple Squad instances
PAO workflow for scanning, drafting, and presenting community responses with human review gate
Detect and set up account-locked gh aliases for multi-account GitHub. The AI reads this skill, detects accounts, asks the user which is personal/work, and runs the setup automatically.
Safely manage multiple GitHub identities (EMU + personal) in agent workflows
Tone enforcement patterns for external-facing community responses
Use reflection-based tests to lock an API contract before the implementation lands.
Reviewer rejection workflow and strict lockout semantics
{what this skill teaches agents}
Expert .NET 10 Full-Stack Developer skill. Use this when implementing new features, vertical slices, or modifying existing logic in the MoreSpeakers application. It covers Domain, Data (EF Core), Managers, and Web (Razor Pages + HTMX).
Apply Result<T>-based feedback patterns in Razor Pages and HTMX flows.
QA Automation Engineer skill. Use this to write or refactor unit tests. Ensures tests follow the project's xUnit, FluentAssertions, and Moq standards.
Database Architect skill. Use this when you need to modify the database schema, add tables, or seed data. This project uses RAW SQL SCRIPTS orchestrated by .NET Aspire, NOT Entity Framework Migrations.
How to write comprehensive architectural proposals that drive alignment before code is written
How to coordinate with squads on different machines using git as transport
Squad branching model: dev-first workflow with insiders preview channel
Microsoft Style Guide + Squad-specific documentation patterns
Shifts Layer 3 model selection to cost-optimized alternatives when economy mode is active.
Detect and set up account-locked gh aliases for multi-account GitHub. The AI reads this skill, detects accounts, asks the user which is personal/work, and runs the setup automatically.
# Model Selection > Determines which LLM model to use for each agent spawn. ## SCOPE ✅ THIS SKILL PRODUCES: - A resolved `model` parameter for every `task` tool call - Persistent model preferences in `.squad/config.json` - Spawn acknowledgments that include the resolved model ❌ THIS SKILL DOES NOT PRODUCE: - Code, tests, or documentation - Model performance benchmarks - Cost reports or billing artifacts ## Context Squad supports 18+ models across three tiers (premium, standard, fast). The
# Skill: nap > Context hygiene — compress, prune, archive .squad/ state ## What It Does Reclaims context window budget by compressing agent histories, pruning old logs, archiving stale decisions, and cleaning orphaned inbox files. ## When To Use - Before heavy fan-out work (many agents will spawn) - When history.md files exceed 15KB - When .squad/ total size exceeds 1MB - After long-running sessions or sprints ## Invocation - CLI: `squad nap` / `squad nap --deep` / `squad nap --dry-run` -
# Personal Squad — Skill Document ## What is a Personal Squad? A personal squad is a user-level collection of AI agents that travel with you across projects. Unlike project agents (defined in a project's `.squad/` directory), personal agents live in your global config directory and are automatically discovered when you start a squad session. ## Directory Structure ``` ~/.config/squad/personal-squad/ # Linux/macOS %APPDATA%/squad/personal-squad/ # Windows ├── agents/ │ ├── {agent-name
Step-by-step release checklist for Squad — prevents v0.8.22-style disasters
Reviewer rejection workflow and strict lockout semantics
Platform detection and adaptive spawning for CLI vs VS Code vs other surfaces
Fix xUnit v3 test projects that compile but show zero discovered tests under dotnet test.
How to coordinate with squads on different machines using git as transport
Team-wide charter and history optimization through skill extraction
Core conventions and patterns for this codebase
Core conventions and patterns used in the Squad codebase
Core conventions and patterns used in the Squad codebase
Never read .env files or write secrets to .squad/ committed files
Never read .env files or write secrets to .squad/ committed files
Add or extend MoreSpeakers Domain Result types with explicit factory methods and structured errors.
Step-by-step release checklist for Squad — prevents v0.8.22-style disasters
Core conventions and patterns for this codebase
# Personal Squad — Skill Document ## What is a Personal Squad? A personal squad is a user-level collection of AI agents that travel with you across projects. Unlike project agents (defined in a project's `.squad/` directory), personal agents live in your global config directory and are automatically discovered when you start a squad session. ## Directory Structure ``` ~/.config/squad/personal-squad/ # Linux/macOS %APPDATA%/squad/personal-squad/ # Windows ├── agents/ │ ├── {agent-name
# Skill: nap > Context hygiene — compress, prune, archive .squad/ state ## What It Does Reclaims context window budget by compressing agent histories, pruning old logs, archiving stale decisions, and cleaning orphaned inbox files. ## When To Use - Before heavy fan-out work (many agents will spawn) - When history.md files exceed 15KB - When .squad/ total size exceeds 1MB - After long-running sessions or sprints ## Invocation - CLI: `squad nap` / `squad nap --deep` / `squad nap --dry-run` -
# Model Selection > Determines which LLM model to use for each agent spawn. ## SCOPE ✅ THIS SKILL PRODUCES: - A resolved `model` parameter for every `task` tool call - Persistent model preferences in `.squad/config.json` - Spawn acknowledgments that include the resolved model ❌ THIS SKILL DOES NOT PRODUCE: - Code, tests, or documentation - Model performance benchmarks - Cost reports or billing artifacts ## Context Squad supports 18+ models across three tiers (premium, standard, fast). The
Team initialization flow (Phase 1 proposal + Phase 2 creation)
Team initialization flow (Phase 1 proposal + Phase 2 creation)
Tone enforcement patterns for external-facing community responses
Squad branching model: dev-first workflow with insiders preview channel
Shifts Layer 3 model selection to cost-optimized alternatives when economy mode is active.
Coordinating work across multiple Squad instances
How to write comprehensive architectural proposals that drive alignment before code is written
Shared hard rules enforced across all squad agents
Standard collaboration patterns for all squad agents — worktree awareness, decisions, cross-agent communication
Standard collaboration patterns for all squad agents — worktree awareness, decisions, cross-agent communication
Defensive CI/CD patterns: semver validation, token checks, retry logic, draft detection — earned from v0.8.22
Safely manage multiple GitHub identities (EMU + personal) in agent workflows
# Skill: CLI Command Wiring **Bug class:** Commands implemented in `packages/squad-cli/src/cli/commands/` but never routed in `cli-entry.ts`. ## Checklist — Adding a New CLI Command 1. **Create command file** in `packages/squad-cli/src/cli/commands/<name>.ts` - Export a `run<Name>(cwd, options)` async function (or class with static methods for utility modules) 2. **Add routing block** in `packages/squad-cli/src/cli-entry.ts` inside `main()`: ```ts if (cmd === '<name>') { const
Update tests when changing APIs — no exceptions
Update tests when changing APIs — no exceptions
Cross-platform path handling and command patterns
Record final outcomes to history.md, not intermediate requests or reversed decisions
# Skill: CLI Command Wiring **Bug class:** Commands implemented in `packages/squad-cli/src/cli/commands/` but never routed in `cli-entry.ts`. ## Checklist — Adding a New CLI Command 1. **Create command file** in `packages/squad-cli/src/cli/commands/<name>.ts` - Export a `run<Name>(cwd, options)` async function (or class with static methods for utility modules) 2. **Add routing block** in `packages/squad-cli/src/cli-entry.ts` inside `main()`: ```ts if (cmd === '<name>') { const
Platform detection and adaptive spawning for CLI vs VS Code vs other surfaces
PAO workflow for scanning, drafting, and presenting community responses with human review gate
Team-wide charter and history optimization through skill extraction
Record final outcomes to history.md, not intermediate requests or reversed decisions
Find and resume interrupted Copilot CLI sessions using session_store queries
Find and resume interrupted Copilot CLI sessions using session_store queries
Cross-platform path handling and command patterns