planning
/planning
Tworzy dokumenty planu z nagłówkiem YAML i śledzi zadania, pomysły oraz błędy w jednym miejscu.
- Autor
- nimbalyst ↗
- Repozytorium
- nimbalyst ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 27.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 27.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Tworzy dokumenty planu z nagłówkiem YAML i śledzi zadania, pomysły oraz błędy w jednym miejscu.
Oryginalny opis (EN)
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.
Jak działa
- Plan Documents
- Tracking Items
- When to Use
- File Naming
- Best Practices
Podgląd SKILL.md
--- 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 a Wiki, 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 a Wiki, a decision usually belongs in its plan doc. - **plans.md**: Plans and features (`#plan`, prefix: `pln`) ### 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
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · nimbalyst/nimbalyst | 100 | MIT |
| iliaal/ai-skills | 100 | MIT |
| open-metadata/openmetadata | 100 | Apache-2.0 |
| davila7/claude-code-templates | 100 | MIT |
| smart-ai-memory/attune-ai | 100 | Apache-2.0 |
| iliaal/whetstone | 100 | MIT |
| doloopz94/virtual-office-muse-ai | 100 | MIT |
| microclaw/microclaw | 100 | MIT |
| jkitchin/skillz | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki cd5af6088253 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 93pi-planning-with-files
Planuje złożone zadania w plikach task_plan.md, findings.md i progress.md, by przetrwać przerwy w sesji. - 90workspace-assistant
Dodaje szybkie zadania i zgłoszenia błędów, śledzi jednorazowe prace i aktualizuje ich statusy w domyślnym projekcie. - 100bits
Śledzi zadania, zgłoszenia i listy rzeczy do zrobienia z zależnościami w narzędziu bits: tworzy zadania, zarządza blokadami, wyszukuje gotową pracę, zajmuje i zwalnia zadania oraz zamyka ukończone. - 100planning-with-files
Tworzy i utrzymuje pliki planu, ustaleń i postępu, żeby wieloetapowy projekt dało się wznowić po /clear. - 98planning-with-files
Organizuje i śledzi postęp złożonych zadań w stylu Manus na plikach task_plan.md, findings.md i progress.md, z automatycznym odzyskiwaniem sesji po /clear. - 95project-progress
Prowadzi długie prace w pliku PROGRESS.md, tak by okno kontekstu zawierało tylko bieżące zadanie i jego plan.