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:
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
Last updated