> For the complete documentation index, see [llms.txt](https://handbook.catalpa.io/the-catalpa-handbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.catalpa.io/the-catalpa-handbook/5.-project-and-product-cycle-management/5.4-post-contract-implementation/stage-3-refine-and-release/release/epic-planning.md).

# Epic planning

* **Outline:** A moment to present and clarify the new Epic.
* **Goal:** Ensure the whole team understands what needs to be done.
* **Duration:** 60 minutes.
* **Frequency:** Before starting a new Epic.

## How-to

1. Open the [Epic Design Document](/the-catalpa-handbook/5.-project-and-product-cycle-management/5.4-post-contract-implementation/stage-3-refine-and-release/release/epics.md#epic-design-document)
2. Read the Summary to make the goal clear to everyone
3. Go over each [User Story](/the-catalpa-handbook/5.-project-and-product-cycle-management/5.4-post-contract-implementation/stage-2-create-and-ideate/the-guide/user-stories.md#how-to-write-a-good-user-story). For each: 
   1. Allow for a Q\&A and take relevant notes.
   2. Estimate using the Day, Days, Week scale.
4. Find dependencies or critical paths. 
5. Sort priorities according to value. **After:** \
   1\. Create a Milestone on Github for the new Epic \
   2\. Add all the User Stories as issues. Tag them as `user story` and associate them to the corresponding Milestone

{% hint style="info" %}
Hint: plan ahead and have this meeting at least 1 week before the ongoing Epic is due
{% endhint %}

{% hint style="info" %}
Check the [Epic Design Document template](https://docs.google.com/document/d/1ev79g21SrUQCI8nf7OQPIYIV9fn2bIhah49K5MApLK8/edit) on Catalpa's Drive
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://handbook.catalpa.io/the-catalpa-handbook/5.-project-and-product-cycle-management/5.4-post-contract-implementation/stage-3-refine-and-release/release/epic-planning.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.