mermaid-collab-dev

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

The CLARIFYING phase discusses each item one at a time to fully understand requirements

The EXPLORING phase gathers context about the project and forms an initial understanding

Transition from brainstorming to rough-draft skill

The VALIDATING phase runs the completeness gate to ensure design is ready for implementation

Use when starting collaborative design work - creates isolated collab sessions with mermaid-collab server

Close out a collab session - archive or delete design artifacts

Detailed procedures for finding, creating, and resuming collab sessions

Start the mermaid-collab server and begin a collab session

The core orchestration loop that processes work items one at a time

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

Use when executing implementation plans with independent tasks in the current session

Detailed execution logic for the executing-plans skill

Verification, drift detection, and snapshot logic for executing-plans

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Fix flagged Kodex topics by generating updated content

Fill in missing sections of incomplete Kodex topics

Correct factually incorrect Kodex topic content

Create new Kodex topics for missing documentation

Update an outdated Kodex topic by analyzing codebase changes since topic was written

Bootstrap a Kodex knowledge base by analyzing codebase structure and creating topic stubs

Create and collaborate on Mermaid diagrams and UI wireframes with real-time preview and team sharing

Validate design completion and transition to implementation phase

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

Bridge brainstorming to implementation through 4 phases - interface, pseudocode, skeleton, and implementation handoff

Phase 4 - Hand off to executing-plans with the dependency graph

Phase 1 - Define the structural contracts of the system

Phase 2 - Define the logic flow for each function

Use when executing implementation plans with independent tasks in the current session

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Plan operational tasks (docker, installs, organization) that skip TDD

Use when implementing any feature or bugfix, before writing implementation code

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

Use when creating or editing UI mockups, screen layouts, or interface designs. Use INSTEAD of ASCII art for any visual UI representation.

Use when project knowledge could help - queries Kodex topics and flags outdated information

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Verify rough-draft phase alignment with design doc

Use when you have a spec or requirements for a multi-step task, before touching code

Use when creating new skills, editing existing skills, or verifying skills work before deployment