Project Management Tools

pair manages work items for you. When you run process skills like /pair-process-implement or /pair-process-plan-stories, pair reads your way-of-working.md adoption file to determine which PM tool to use, then creates and updates issues, stories, and tasks automatically.

How It Works

1. You choose a PM tool during project bootstrap (or change it later in way-of-working.md)
2. pair reads the config every time a process skill runs
3. pair creates and updates work items — initiatives, epics, stories, tasks — in the configured tool
4. Status flows automatically — completing a task updates the story, completing all stories updates the epic, and so on

You focus on the work. pair keeps the board in sync.

Supported Options

Choosing a Tool

• Starting solo or want zero dependencies? Use Filesystem — everything lives in your repo as Markdown files.
• Team on GitHub? Use GitHub Projects — issues, labels, and project boards you already know.
• Want a dedicated PM tool? Use Linear — clean UI, fast workflows, great API.

You can switch between tools at any time by updating way-of-working.md. Your adoption files and Knowledge Base stay the same.

The Mapping Model

pair uses a consistent hierarchy regardless of tool:

Initiative (strategic goal)
└── Epic (feature set)
    └── User Story (deliverable increment)
        └── Task (implementation step)

Each PM tool maps this hierarchy to its own concepts:

Configuration

All PM tool configuration lives in one place: .pair/adoption/tech/way-of-working.md. Each tool guide shows the exact configuration lines to add.

Related

• AI Coding Tools — set up your AI assistant
• Developer Journey — the full development lifecycle
• Adoption Files concept — how adoption files work