# Plan epics (features)
### Plan features
To plan a feature in a sprint:
* Select the period in the period picker (top left)
* Click on ***Feature Plan***
* **Search** on the name of the feature in the *unassigned* column.
* **Drag and drop the** feature from *unassigned* to the desired sprint
### Add details
The **story points** of a feature are defined by the number of story-points of the underlying stories (excluding dependency stories from other teams – those are kept separately). If needed, one can also directly define the story points at feature level. This can be useful in case underlying stories are not yet created in Jira, but we already want to highlight the story points at feature level.
The **RAG** (**R**ed, **A**mber, **G**reen) indicator visually represents the health status of the feature. The color codes typically mean the following:
* Green means the issue is on track.
* Amber means a serious risk or issue occurs but mitigation is still possible.
* Red means a major risk or issue occurs and attention from management and peers is needed.
Issues and risks can be added the RAG comment field.
To add details to a feature:
* Click on the **details toggle** in the top navigation bar
* Update the field.
### Swimlanes
Click **View Options > Epic Swimlanes** to view work items grouped by epic in a swimlane. Work items without parent epics or with parent epics outside of the PI are grouped in a separate **“other”** swimlane. The Epic Swimlanes view is available on both the **Plan** and **Team Breakout** pages.
---
# Agent Instructions: 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:
```
GET https://docs.ativo.io/pi-planning/plan-epics-features.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.