mpi-nimbalyst-sync

Coordinate MPI Kanban with Nimbalyst modes via dry-run import/export workflows.

1|Updated May 13, 2026

Search Tags:#kanban #mapping #task-tracking #mode-switch #interop #dry-run #nimbalyst

Ready to run

npx skills add https://github.com/MadPonyInteractive/mpi-kanban --skill mpi-nimbalyst-sync

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mpi-nimbalyst-sync
Source: https://github.com/MadPonyInteractive/mpi-kanban/tree/main/skills/mpi-nimbalyst-sync
Command: npx skills add https://github.com/MadPonyInteractive/mpi-kanban --skill mpi-nimbalyst-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate MPI Kanban with Nimbalyst interop to prevent live dual-writing and keep boards and trackers consistent during interop operations.

Core Features & Use Cases

Interop detection and mode-switch proposals to safely navigate between file and Nimbalyst modes.
Dry-run planning for import/export and ID mapping to surface conflicts before any mutation.
Reference-guided operations using the shared mpi-lib documentation to align task state and tracker data.

Quick Start

Ask me to perform a dry-run for switching to Nimbalyst mode and map MPI task IDs to Nimbalyst trackers.

Frequently Asked Questions about mpi-nimbalyst-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prevent dual-writing when syncing Kanban boards with Nimbalyst?▼

Preventing dual-writing during Nimbalyst interop involves using mode-switch proposals to safely navigate between file and Nimbalyst source-of-truth modes before any data mutation occurs.

Can I do a dry-run for mapping Kanban task IDs to Nimbalyst trackers?▼

Yes, you can perform a dry-run for import/export workflows and ID mapping to surface potential conflicts and preview changes before any actual state mutation is applied to the Kanban board.

What is the best way to switch Kanban tracking between file and Nimbalyst modes?▼

Switching modes is best handled by generating mode-switch proposals that reference shared mpi-lib documentation, ensuring task state alignment before updating tracker data on explicit approval.

Does the Nimbalyst interop process require explicit approval before updating task state?▼

Yes, the Nimbalyst interop process reads and references shared mpi-lib docs and interop.json, but it only updates task state and tracker data upon your explicit approval.

Why should I use a dry-run for Kanban and Nimbalyst import/export operations?▼

Using a dry-run for import/export operations detects ID mapping conflicts and previews state changes, preventing inconsistent boards and accidental data overwrites during Nimbalyst interop.