Join a project that already uses pair

What a new team member does on day one in a repository that already has .pair/, adoption files and skills.

Goal: be productive in a pair-enabled repository without installing or configuring anything that is already there.

Prerequisites

Pull the repository
- .pair/adoption/, the bridge files (AGENTS.md, CLAUDE.md, .cursor/rules/) and usually .pair/knowledge/ and .claude/skills/ are committed. Nothing to install into the project.
Install the CLI, if the project's skills call it
- With pair-cli: npm install -g @foomakers/pair-cli (or pnpm add -g), then pair-cli --version. Match the version your team pinned, if package.json lists @foomakers/pair-cli use that one with npx pair-cli.
Start your assistant in the repository
- It reads the bridge file for your tool, which points at .pair/. Ask it to describe the project's architecture and way of working: the answer should come from .pair/adoption/.
Ask what to do
- In your assistant: /pair-next. It reads the board and suggests the next step; /pair-process-implement <id> picks up a Ready story.

A new session knows the tech stack and the quality gate command without being told.
/pair-next proposes a step that matches the board.