Planning
Create structured plan documents and track work items using YAML frontmatter.
Install
npx skills add nimbalyst/nimbalyst --skill planning -g -a claude-code -y- Repository
- nimbalyst/nimbalyst2k
- Category
- Engineering
- Updated
- 4d ago
- License
- MIT
- Context cost
- Lightabout 1,042 tokens
- Runs scripts
- No, instructions only
What it does
Create structured plan documents and track work items using YAML frontmatter. Use when the user wants to plan a feature, track progress, log bugs/tasks/ideas, or organize project work.
Planning and Tracking System
Nimbalyst uses structured markdown documents with YAML frontmatter for planning and tracking work.
Plan Documents
Plans live in nimbalyst-local/plans/ with YAML frontmatter:
---
planStatus:
planId: plan-[unique-identifier]
title: [Plan Title]
status: draft
planType: feature
priority: medium
owner: [owner-name]
stakeholders: []
tags: []
created: "YYYY-MM-DD"
updated: "YYYY-MM-DDTHH:MM:SS.sssZ"
progress: 0
---
Status Values
draft: Initial planning phaseready-for-development: Approved and ready to startin-development: Currently being worked onin-review: Implementation complete, pending reviewcompleted: Successfully completedrejected: Plan has been rejectedblocked: Progress blocked by dependencies
Plan Types
feature: New feature developmentbug-fix: Bug fix or issue resolutionrefactor: Code refactoring/improvementsystem-design: Architecture/design workresearch: Research/investigation taskinitiative: Large multi-feature effortimprovement: Enhancement to existing feature
Tracking Items
Track bugs, tasks, ideas, and other items in nimbalyst-local/tracker/:
- [Brief description] #[type][id:[idPrefix]_[ulid] status:[default-status] priority:medium created:YYYY-MM-DD]
CRITICAL: Custom Tracker Types
Before creating any tracker item, always check .nimbalyst/trackers/*.yaml in the workspace root for custom tracker type definitions. Each YAML file defines a tracker type with:
type: The type name used in#[type][...]syntax (e.g.,devblog-post)idPrefix: The prefix for generated IDs (e.g.,devproducesdev_abc123)fields: Available fields including status options with custom valuessync: Whether items sync to the team (shared/local/hybrid)
