> 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/task-management/item-types-and-fields.md).

# Item Types and Fields

Nimbalyst includes six built-in tracker types. Each has its own status workflow, fields, and color-coded icon. The type determines which columns appear on the kanban board and which fields are available in the detail view.

### Bug

For tracking defects and issues.

* **Icon:** Bug report (red)
* **Statuses:** To Do, In Progress, In Review, Done
* **Fields:** Title, Status, Priority, Owner, Description

### Task

For general work items and to-dos.

* **Icon:** Task (blue)
* **Statuses:** To Do, In Progress, In Review, Done
* **Fields:** Title, Status, Priority, Owner, Description

### Feature

For new capabilities and enhancements.

* **Icon:** Rocket (green)
* **Statuses:** To Do, In Progress, In Review, Done
* **Fields:** Title, Status, Priority, Owner, Description, Release Version, Release Notes

### Idea

For capturing ideas before they become work items.

* **Icon:** Lightbulb (yellow)
* **Statuses:** New, Considering, Accepted, Rejected
* **Fields:** Title, Status

### Decision

For recording architectural and product decisions with context.

* **Icon:** Gavel (purple)
* **Statuses:** To Do, In Progress, Decided, Implemented
* **Fields:** Title, Status, Chosen (the decision made), Priority, Owner, Stakeholders, Tags

### Plan

Nimbalyst supports two approaches to planning:

* **Quick plans (via /plan for Claude Code):** Uses Claude Code's default planning model — a temporary plan is created, given a name, used for implementation, and then discarded. These plans are not integrated with the tracker system.
* **Long-lived plans:** Write a thoughtful plan in markdown that outlines goals, strategy, and features. Update it with your architecture and implementation overview. Keep this as a long-lived document. To work this way, create a custom `/` command or skill (e.g., `/spec`) and have it integrate with the tracker system. This approach keeps your plans visible, versioned, and connected to your task tracking.

For larger initiatives with progress tracking.

* **Icon:** Flag (blue)
* **Statuses:** Draft, Ready for Development, In Development, In Review, Completed, Rejected, Blocked
* **Fields:** Title, Status, Plan Type, Priority, Progress (0-100%), Owner, Stakeholders, Tags, Start Date
* **Plan Types:** System Design, Feature, Bug Fix, Refactor, Documentation, Research

### Priority Levels

All item types that support priority use the same four-level scale:

| Priority | Use For                                       |
| -------- | --------------------------------------------- |
| Critical | Blocking issues that need immediate attention |
| High     | Important work that should be done soon       |
| Medium   | Standard priority (default)                   |
| Low      | Nice-to-have or can wait                      |


---

# 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/task-management/item-types-and-fields.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.