> For the complete documentation index, see [llms.txt](https://frostember-studios.gitbook.io/frostboard/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://frostember-studios.gitbook.io/frostboard/getting-started/editor.md).

# Workflow

### Board Management (Multi-Board)

Frostboard supports multiple separate boards in a single project, which is ideal for separating the work of different teams (Programmers, Artists) or different projects.

By clicking on the current board's name in the top left, you open a menu where you can:

* Switch between existing boards.
* Select `Create New Board...` to create a new, clean board.
* Rename or delete the currently displayed board.

Each board has its own set of tasks, attachments, milestones, and labels. Settings (like element visibility) are shared across boards for a single user.

### Anatomy of a Task: The Detail Panel

Double-clicking on any card opens the detail panel, which is the heart of the system. It allows for comprehensive management of all aspects of a task.

#### Basic Fields

* **Title:** A short and descriptive name for the task.
* **Git Branch:** A field for programmers to insert the name of the Git branch they are working on. It helps to keep track of where the functionality is being developed.
* **Description:** The main description of the task. It supports **Markdown** formatting for better readability. Clicking on the text reveals an edit field. After finishing edits and clicking **✓ Done Editing**, the text is formatted.
  * Supported tags: `**bold**`, `*italic*`, `~~strikethrough~~`, `` `code` ``, `# Heading 1`, `## Heading 2`, `- Bullet point`.

#### Attributes and Planning

* **Type & Priority:** Basic attributes for quick classification (Bug, Feature, Chore) and determining importance (Low, Medium, High, Critical).
* **Milestone:** Assigning a task to a specific sprint or milestone (e.g., "Alpha", "Beta 1.1"). Milestones are managed via the **Milestones** button in the top toolbar.
* **Time Tracking & Story Points:**
  * **Story Points:** An agile estimate of the task's complexity.
  * **Est. Hours:** Estimated time required to complete the task, in hours.
  * **Spent Hours:** Time actually spent on the task.
* **Dates (Start/Due):** Option to set a time frame. The calendar icon (📅) opens an interactive date picker.

#### Context and Linking

* **Assignees:** Assigning one or more team members to a task. The team is managed in the **Settings** window.
* **Labels:** Colored labels for more detailed categorization. Labels are managed via the **Labels** button in the top toolbar.
* **Dependencies:** Links between tasks. You can define that a task is blocked by another (`Blocked by`) or that it blocks others (`Blocking`).
* **Project References:** Ability to drag any asset from the project (script, prefab, material) to create a direct link. Clicking the reference will ping the asset in the Project window.

#### Attachments and Collaboration

* **Attachments:**
  * **Select File...:** Upload an image from your computer.
  * **Capture Scene View:** Creates a screenshot of the active Scene View window.
  * **Capture Game View:** Creates a screenshot of the Game window (works best in Play Mode).
* **Comments & Activity Log:** Users can write standard text comments. The system also automatically generates entries for key changes (moving between columns, renaming, etc.), which are displayed as grayed-out system comments.


---

# 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://frostember-studios.gitbook.io/frostboard/getting-started/editor.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.