> For the complete documentation index, see [llms.txt](https://docs.nimbalyst.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nimbalyst.com/visual-editors-powered-by-ai/markdown-wysiwyg/set-document-type.md). # Set Document Type Set Document Type turns a markdown document into a tracked Plan or Decision from the editor's Actions menu, without hand-writing YAML frontmatter. **Set Document Type** promotes the markdown document you are looking at into a tracked item. Pick a type and Nimbalyst writes the tracker frontmatter for you, the tracker header appears at the top of the document, and the document starts showing up on the kanban board alongside everything else in your tracker. It is the one-click version of the [YAML frontmatter](/task-management/creating-items.md) route to creating a tracker item. ### Where to find it Open the **three-dot Actions menu** at the top right of a markdown document and hover **Set Document Type**. A submenu lists the available types. The action is available when all of the following are true: * The file is a markdown file (`.md`) * You are in WYSIWYG view, not raw Markdown view * The document is not already owned by a tracker item. In the tracker's own document view the type lives on the record, so the menu item is hidden The same submenu is on the floating document actions button inside the editor. ### The available types Two types are offered: | Type | Icon | What it is for | | ------------ | -------------- | -------------------------------------------------------------------------------- | | **Plan** | Flag (blue) | A larger initiative with a status workflow and a progress percentage | | **Decision** | Gavel (purple) | An architectural or product decision, with the chosen option recorded as a field | These are the two built-in types designed to live as a whole document rather than as a row on a board. Bugs, tasks, features, and ideas are usually short enough to belong in the tracker itself, so they are not offered here. See [Creating Items](/task-management/creating-items.md) for those. ### Other types, and asking the agent The submenu is limited to Plan and Decision, but the underlying mechanism is not. Any tracker type can own a whole document as long as its definition sets `modes.fullDocument: true`, so you can ask the agent for the ones the menu doesn't list: > "Make this document a milestone" "Turn this into a customer-feedback item" The agent writes the `trackerStatus` frontmatter, and the tracker picks the file up on its next scan exactly as if you had used the menu. It can also create the type first — ask it to define a custom tracker type and it writes the YAML into `.nimbalyst/trackers/`. See [Custom Tracker Types](/task-management/custom-tracker-types.md). Among the built-ins, **Milestone** and **Release** are full-document types too, so both work when asked for by name even though they are absent from the menu. {% hint style="warning" %} Asking for a type that is inline-only (Bug, Task, or Idea) is a quiet no-op. The frontmatter lands in the file and looks right, but the tracker ignores it and the document never appears on the board. The same is true of a custom type whose YAML leaves `fullDocument` at `false`. If you asked for a type and nothing showed up, check `modes.fullDocument` in that type's definition. {% endhint %} ### What it does to the document Choosing **Plan** writes a `planStatus` block at the top of the file with the plan's default fields: ```yaml --- planStatus: planId: "plan_1740000000000_a1b2c3" title: "" status: "draft" planType: "feature" priority: "medium" progress: 0 owner: "" stakeholders: [] tags: [] created: "2026-08-24" updated: "2026-08-24T00:00:00.000Z" --- ``` Choosing **Decision** writes a `decisionStatus` block with the decision fields (`decisionId`, `status`, `chosen`, `priority`, `owner`, `stakeholders`, `tags`). Once the frontmatter is there: * A tracker header appears at the top of the document showing the type's fields. Edit status, priority, owner, and the rest from that header. * The item appears in the tracker panel and on the kanban board. * Edits flow both ways. Change the status in the tracker UI and the file updates; change it in the file and the tracker updates. * The document is marked dirty and autosave writes it to disk. Switch to raw Markdown view from the same three-dot menu to see the frontmatter block directly. ### Changing or removing the type Reopen the submenu at any time. The current type carries a checkmark. Picking the other type converts the document. When a type is set, a **Remove Type** entry appears at the bottom of the submenu. It strips the tracker frontmatter and the document goes back to being an ordinary markdown file, dropping off the board. {% hint style="warning" %} Setting a type replaces the document's entire frontmatter block, and **Remove Type** deletes the entire frontmatter block. Any other keys you keep up there (a `description`, tags used by a static site generator, anything an extension reads) are lost. If your document has frontmatter you care about, copy it somewhere first, or edit the `trackerStatus` block by hand in raw Markdown view instead. {% 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://docs.nimbalyst.com/visual-editors-powered-by-ai/markdown-wysiwyg/set-document-type.md?ask=&goal= ``` `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.