New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Planning

by nimbalyst in nimbalyst/nimbalyst

Create structured plan documents and track work items using YAML frontmatter.

MITAuto-check passedDevelopment

Install Planning

skills CLI
$ npx skills add nimbalyst/nimbalyst --skill planning -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install nimbalyst/nimbalyst planning --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/nimbalyst/nimbalyst.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/extensions/planning/claude-plugin/skills/planning .claude/skills/planning && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
planning
GitHub stars
1.8k
Token cost
~1.1k tokens
SKILL.md length
468 words
Files
1
Skills in repo
14
Repo updated
First seen
Licence
MIT

At a glance

Create structured plan documents and track work items using YAML frontmatter.

  • The user wants to plan a feature
  • SKILL.md covers Plan Documents, Tracking Items, When to Use and File Naming, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Log bugs/tasks/ideas

What it does

Planning is an agent skill from nimbalyst/nimbalyst. 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.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. The repository describes itself as: Nimbalyst - The open-source visual workspace for Claude Code, Codex, and OpenCode. Run multiple coding agents in parallel, edit their work visually in markdown, mockups, and… The licence is MIT.

When your agent uses it

  • The user wants to plan a feature
  • Log bugs/tasks/ideas
  • Organize project work

Example prompts

  • “/planning”

What it can do on your machine

Read from SKILL.md and the folder at commit a3dbdb4. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml and markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Planning loads about 1.1k tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 468 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~48
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from nimbalyst/nimbalyst at commit a3dbdb4, republished under its MIT licence (© nimbalyst). 468 words, ~1,097 tokens.

Download SKILL.mdSave it as .claude/skills/planning/SKILL.md (or your agent's skills folder).
name
planning
description
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:

yaml
---
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 phase
  • ready-for-development: Approved and ready to start
  • in-development: Currently being worked on
  • in-review: Implementation complete, pending review
  • completed: Successfully completed
  • rejected: Plan has been rejected
  • blocked: Progress blocked by dependencies
Plan Types
  • feature: New feature development
  • bug-fix: Bug fix or issue resolution
  • refactor: Code refactoring/improvement
  • system-design: Architecture/design work
  • research: Research/investigation task
  • initiative: Large multi-feature effort
  • improvement: Enhancement to existing feature

Tracking Items

Track bugs, tasks, ideas, and other items in nimbalyst-local/tracker/:

markdown
- [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., dev produces dev_abc123)
  • fields: Available fields including status options with custom values
  • sync: Whether items sync to the team (shared/local/hybrid)

Always use the exact type name from the YAML when creating items. Do not substitute a built-in type when a custom type matches the user's intent.

Built-in Tracker Types
  • bugs.md: Issues and defects (#bug, prefix: bug)
  • tasks.md: Work items and todos (#task, prefix: tsk)
  • ideas.md: Concepts to explore (#idea, prefix: id)
  • decisions.md: Important decisions (#decision, prefix: dec). Not every choice needs one. If the project has Pages, follow its "How we write this wiki" page: mark the decision in the page it affects, and add a decision item only when no single page owns it, work hangs off it, it isn't settled, or its reasons don't fit in the mark. Without Pages, a decision usually belongs in its plan doc.
  • plans.md: Plans and features (#plan, prefix: pln)
Show full SKILL.md (173 more words)Show less
Custom Tracker Types (per-workspace)

Defined in .nimbalyst/trackers/*.yaml. Examples:

  • feature-requests.md (#feature-request, prefix: feat)
  • tech-debt.md (#tech-debt, prefix: debt)
  • devblog-posts.md (#devblog-post, prefix: dev)
  • Any other type defined in the workspace's YAML files

When to Use

  • Creating plans: When user wants to plan a feature, project, or initiative
  • Tracking items: When user mentions bugs, tasks, ideas, or wants to log something
  • Progress updates: When completing work, update plan status and progress
  • Implementation: Use /implement to execute a plan with progress tracking
  • Board cleanup: Use /session-cleanup to tidy the Sessions board -- fix session phases, mark finished work complete, and flag old sessions to archive
  • Getting more from Nimbalyst: Use /planning:nimbalyst-coach to review this project and recent sessions and suggest extensions, features, and agent-instruction changes

File Naming

  • Plans: nimbalyst-local/plans/[descriptive-name].md (kebab-case)
  • Trackers: nimbalyst-local/tracker/[type]s.md (pluralize the type name)

Best Practices

  • Always check .nimbalyst/trackers/ for custom types before using built-in types
  • Keep plans focused on a single objective
  • Update progress regularly as work proceeds
  • Use appropriate priorities (low, medium, high, critical)
  • Link related plans and tracker items
  • Include stakeholders who need visibility

© nimbalyst, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in packages/extensions/planning/claude-plugin/skills/planning of nimbalyst/nimbalyst.

Open the folder on GitHubat commit a3dbdb4

Compare with similar skills

Planning next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Planning compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Planning this skillnimbalyst/nimbalyst1.8k—~1.1kAutomated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k24 repos~4.2kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT
Greplooponyx-dot-app/onyx32k4 repos~3.3kAutomated safety check: PassMIT

Similar skills

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Typescript Advanced Types

    rolling-scopes/rsschool-app

    Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.

    10k GitHub starsUsed in 24 repos~4.2k tokens
    DevelopmentAuto-check passed

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

  • Guidelines

    akash-network/node

    Behavioral guidelines to reduce common LLM coding mistakes. An agent skill from akash-network/node.

    1.1k GitHub starsUsed in 22 repos~577 tokens
    DevelopmentAuto-check passed

More from nimbalyst/nimbalyst

All 14 skills in this repo

  • Knowledge Graph

    nimbalyst/nimbalyst

    Write a project's knowledge pages in Nimbalyst Pages -- record what people said and decided in the page it affects, keep typed pages for the things the team tracks (its own types, such as modules…

    1.8k GitHub stars~3.5k tokensUpdated 2 days ago
    Auto-check passed

  • Knowledge Setup

    nimbalyst/nimbalyst

    Set up or check a project's knowledge pages in Nimbalyst Pages -- install the editable "How we write this wiki" guide page, define the team's own page types (and subtypes) and the named relations…

    1.8k GitHub stars~1.8k tokensUpdated 2 days ago
    Auto-check passed

  • Canvas

    nimbalyst/nimbalyst

    Author Nimbalyst Project Canvas boards (.canvas files) — an infinite canvas whose cards are live editors for real workspace files and shared documents, arranged spatially and wired with edges.

    1.8k GitHub stars~2.6k tokensUpdated 2 days ago
    Auto-check passed

  • Datamodellm

    nimbalyst/nimbalyst

    Create visual data models for database schemas using Nimbalyst's DataModelLM editor.

    1.8k GitHub stars~713 tokensUpdated 2 days ago
    Auto-check passed

  • Excalidraw

    nimbalyst/nimbalyst

    Create diagrams and visual drawings using Excalidraw (.excalidraw files).

    1.8k GitHub stars~1.4k tokensUpdated 2 days ago
    Auto-check passed

  • Extension Development

    nimbalyst/nimbalyst

    Build, install, and hot-reload Nimbalyst extensions using MCP tools.

    1.8k GitHub stars~1.5k tokensUpdated 2 days ago
    Auto-check passed

Categories

Questions about Planning

What does Planning do?

Create structured plan documents and track work items using YAML frontmatter. Planning is an agent skill from nimbalyst/nimbalyst. Create structured plan documents and track work items using YAML frontmatter.

When should I use Planning?

Planning fits situations like: the user wants to plan a feature; log bugs/tasks/ideas; organize project work.

How do I install Planning in Claude Code?

Run `npx skills add nimbalyst/nimbalyst --skill planning -a claude-code`. Or copy the skill folder (packages/extensions/planning/claude-plugin/skills/planning in nimbalyst/nimbalyst) into .claude/skills/planning in your project. Claude Code loads it when a task matches its description.

How do I install Planning in Codex?

Run `npx skills add nimbalyst/nimbalyst --skill planning -a codex`. Or copy the skill folder (packages/extensions/planning/claude-plugin/skills/planning in nimbalyst/nimbalyst) into .agents/skills/planning in your project. Codex loads it when a task matches its description.

Can I use Planning in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nimbalyst/nimbalyst --skill planning -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/planning, .gemini/skills/planning, .github/skills/planning and .opencode/skills/planning in your project.

What does Planning need to run?

SKILL.md names no scripts, command-line tools or credentials: Planning is instructions for the agent only.

Does Planning access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Planning safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Planning use?

Planning is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Planning use?

About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Planning?

Skills that share tags, products or a category with Planning: Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars) and Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Planning?

nimbalyst (a GitHub organization) maintains it in nimbalyst/nimbalyst, which has 1,847 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 5, 2026.

Source: nimbalyst/nimbalyst on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.