# For product managers

A PM's path through EasyCode: tasks on the board, specs written with the team, workflows with gates, and your tracker.

## What does EasyCode do for a PM?

EasyCode puts the work and the agents in one place. You write the task and its spec, your team's agents build it, and
the work stops at the gates you care about until a person decides. You don't need a harness to do your part: the
**Board**, task documents and gate decisions all work in the web app.

## Your path

Follow these pages in order. Each line says why it matters to you.

### Get set up

1. [Quickstart](/setup/quickstart): accept your invite and find your org's **Home**, **Board** and **Products**.
2. [Roles and access](/overview/roles-and-access): what your role lets you see and change, and how a guest differs
   from a member.
3. [Jira and Linear](/setup/jira-and-linear): link your tracker, so tickets and EasyCode tasks stay in step.

### Plan the work

4. [Workflows, gates and the board](/guides/workflows-and-the-board): make tasks with **New task**, use **Link a
   ticket** to tie one to your tracker, and move cards through **Backlog** and **To do**.
5. [Write a spec with your team](/guides/write-a-spec): a task's **Documents** hold the spec. Edit it together, leave
   comments, and use **Request a review** before anyone builds.
6. [From idea to merged PR](/scenarios/idea-to-merged-pr): how a task becomes a spec, a session and a pull request.

### Decide at the gates

7. [Workflows, gates and the board](/guides/workflows-and-the-board): a workflow run waits at a gate. You
   **Approve**, **Request changes** or **Reject**, and the agent carries on from your answer.
8. [From acceptance criteria to QA sign-off](/scenarios/acceptance-criteria-to-qa): the criteria you write become
   what QA checks and proves.
9. [Ship and announce a feature](/scenarios/ship-and-announce): from merged work to the people who need to hear about
   it.

### See it end to end

10. [From invite to merged PR](/walkthroughs/invite-to-merged-pr): the screens a new member sees, from the invite to
    a merged pull request.
11. [Onboard a team](/scenarios/onboard-a-team): when you bring a whole team in.

## Can I start the work myself?

Yes. **Run workflow** on a task picks one of your org's published workflows and asks for its inputs. On the web, the
run is made and waits for a session: **Open the run** shows where it stands, and **Open in desktop** starts the session
in the desktop app.

> **Gated**
>
> The **Board** and **Workflows** follow your org's modules, and guests don't see **Workflows** or the **Library**.
> EasyCode staff can pause a feature for an org with a kill switch: [`runs`](/reference/kill-switches-and-modules#runs) stops workflow runs, [`documents`](/reference/kill-switches-and-modules#documents) stops task documents, and [`trackers`](/reference/kill-switches-and-modules#trackers) stops tracker sync.

## Where next

- [How it fits together](/overview/how-it-fits-together): products, teamspaces and tasks in one picture.
- [Glossary](/reference/glossary): the words EasyCode uses, such as gate, checkpoint and run.
- [Troubleshooting](/help/troubleshooting) when a ticket or a run doesn't show up.
