# From a meeting to epics and plans

You give your agent a meeting transcript saved as a file, and it creates epics, writes plans from your project’s template and links them by dependencies.

- **6 minutes** (reading time)
- **Before you start**: Claude Code connected to featureloom, the Writes plans right for your consoles, a meeting transcript in a text file

Download the recording: [From a meeting to epics and plans (MP4)](https://featureloom.com/_astro/film-en.CLBnjyUT.mp4). All the steps in one recording, narrated.

## 1. Save the transcript as a file

Make the transcript with the tool you use in meetings and save it as a text file, client-meeting.txt for example. No bot joins your meeting: the file is yours.

Save the file in the folder you start Claude Code in, so your agent can read it.

## 2. Send the command with the Planner prompt

Start Claude Code in that folder and send the command. Your agent receives the Planner prompt, which says how to turn material into plans on the board.

```sh
featureloom planner
```

Then point it to the file and say what you expect. For example:

```sh
Read the file client-meeting.txt and break it down into epics and plans in the Invoices project. Record the order as dependencies. At the end, list the plans’ keys and names.
```

> When the console asks to use featureloom’s tools, allow it.

## 3. See how your agent works

The Planner prompt takes your agent step by step: pick the project (`list_projects`) and read its plan template (`get_plan_template`), check which plans and epics already exist (`list_plans`, `list_epics`) so nothing is duplicated, and create an epic for a topic that has none (`create_epic`).

Your agent creates the plans in the template’s sections, each with its topic’s epic and the Realizer prompt (`create_plan`). One plan is one piece of work that one agent session realizes whole. Your agent records the order as dependencies (`add_link`): the plan that waits names the plan it waits for.

The prompt says to write only what follows from the material, and to name a choice the meeting left open in the plan, with a recommendation. At the end your agent lists the plans’ keys and names.

## 4. Check the board

Refresh the board. The new plans are in the column marked with the backlog state, Planned in a new project. Their cards say For a console: Realizer, so the plan is waiting for an agent with that prompt.

A plan that waits for another says so on its card, waits on INV-14 for example. The filters above the columns narrow the board to one epic, and the epics your agent created are in the menu, on the Epics screen.

![The Planned column on the board narrowed to the epic the agent created: its plans INV-53 to INV-56, each marked For a console Realizer, three of them waiting on another plan, for example INV-54 waits on INV-53](https://featureloom.com/_astro/step-4-en.Cvmtfj6Z_ZFWlhB.webp)

One epic’s plans on the board

## 5. Fix what needs fixing

You change a plan your agent wrote like any other: the Edit button above the document. Every save that changes the text is a new version in the document’s history.

You add or remove a dependency on the plan’s screen, under Dependencies. The tutorial Epics and Order: what to take first shows how to read the epic’s order and pick the plan to start with.

![The screen of the plan INV-54 Central bank exchange rate stored on the invoice with Dependencies unfolded: the plan waits on INV-53 Invoice currency field (GBP, EUR, USD) and INV-11 Currencies and NBP exchange rates, and unlocks INV-55 and INV-56](https://featureloom.com/_astro/step-5-en.DemSSNvR_Z2e8far.webp)

The plan’s dependencies

## Good to know

- One plan from a short request in the console: the tutorial Your agent writes a plan from a console conversation shows it.
- It works without an agent too: paste the transcript or send a document on the Capture screen. The tutorial A plan from pasted text or a PDF or Word document shows how.
- A console acts with your rights. Without the Writes plans right, your agent creates no plan and no epic. An administrator grants rights on the People screen.
- Every new organization has the Planner and Realizer prompts. You find them under Prompts in the menu and can change them, for example to add how your team splits work into plans.
- Working from a specification rather than a meeting? [Spec-driven development with Claude Code](https://featureloom.com/en/use-cases/spec-driven-development-with-claude-code/) shows the way from your spec to accepted work.

Updated: November 8, 2026

## Next: Epics and Order: what to take first

Epics group plans, dependencies say what waits on what, and Order shows where to start.

[See the tutorial](https://featureloom.com/en/tutorials/epics-and-order-what-to-take-first/)