# Plans

Source: https://docs.coderhelm.com/getting-started/plans

Describe a bigger change in your own words; CoderHelm reads your code and drafts a plan of tickets you can edit before anything runs.

A **plan** turns a change too big for one ticket into an ordered list of tasks. Each task becomes a GitHub issue or a Jira ticket, and each one becomes a run.

## Make a plan [#make-a-plan]

1. Open **Plans** → **New plan**.
2. Answer **What do you want to change?** in your own words. For example: "Let people export their invoices as CSV from the billing page."
3. CoderHelm reads your code (and any connected tools, such as your issue tracker or docs) while it writes. You see the plan appear as it streams, and you can keep chatting to change it.
4. Pick where the tasks go: **GitHub Issues**, or **Jira Tickets** once Jira is connected.
5. Click **Save plan**.

You can also start from a **template**: save a plan you like as a template, then reuse it from **Templates**.

## Approve and run [#approve-and-run]

Open the plan. It has an overview, the tasks, the runs and pull requests made from it, a spec, and a list of what the chat looked at.

- **Approve all and start** creates every ticket and starts the runs in order.
- Or approve tasks one by one. Approving the last one starts the plan.

Nothing is created in GitHub or Jira, and no code changes, until you approve.